LightBlog

mercredi 28 septembre 2016

Samsung: 60% of Recalled Note 7s Exchanged in U.S and South Korea, 90% of Users Choose new Note 7

Samsung has been dealing with their Galaxy Note 7 replacement program for close to a month now. At first, things were slow to start as the company didn't have new, safe units for customers to swap out. So those who participated in the replacement program early were forced to get a refund or switch to another Samsung phone like the Galaxy S7 or Galaxy S7 Edge. This actually caused a number of people to ignore the replacement program for the first couple of weeks.

A week ago, Samsung confirmed that 500,000 replacement units of the Galaxy Note 7 had arrived in the United States and other shipments were on the way to other countries around the world. Since replacement units have become available Samsung says 90% of those who have returned their Galaxy Note 7 have opted to get one of these newer units. Samsung says they are humbled by the loyalty their customers have with the product and with the company.

They have also announced that more than 60% of defective Galaxy Note 7 units have been replaced in both the United States as well as South Korea. The company also notes that over 80% of their Galaxy Note 7 customers in Singapore have participated in the exchange program. Samsung does note that "there have been only a small number of reported incidents," even though it has likely been higher than expected.

Samsung doesn't want to see anyone else get hurt from their products and they need to do a lot of work to repair the reputation they and the Galaxy Note 7 has received lately. Although sadly, these issues might continue to surface as we've seen replaced Galaxy Note 7 devices continue to have issues with the battery and one reportedly caught on fire in China just this week. Samsung hasn't released an official statement regarding these new units having issues, but we expect the company to confirm or deny the reported cases in the near future.

Source: Samsung Newsroom



from xda-developers http://ift.tt/2drVpaf
via IFTTT

Compilation: OnePlus September Software Edition AMA

Yesterday, the OnePlus team took to Reddit's Android subreddit to field questions and provide answers. This AMA (Ask Me Anything) session was attended by Brian (Head of ROM Product), Aaron (Android Technical Lead), Omega (ROM Dev Lead), Bradon (Community/Marketing) and Carl (Head of Global). The AMA was intended to be software focused, but the team answered a fair few general questions as well.

Here is a compilation of everything we've learned from the Reddit AMA:

General Questions and Future Plans

bad-_-horseHas your focus shifted from providing good phones on a budget or will you still aim to have good and cheap phones? Will you release multiple tiers of phones at once?

Bradon: We've never made a "cheap" phone, and pricing has never been a main focus for us. We start by creating the best products we can and go from there. That said, we are pretty proud of our streamlined operations which allow us to be competitive in terms of pricing.

nikigx2/u/Carpe02 are there any plans on releasing OnePlus smartwatch?

Carl: Nope

quicksilver101Any reason on why OnePlus does not incorporate FM Radio functionality into the devices? The OnePlus 3 is missing FM Radio, and FM still continues to be a favorite feature for those who are not looking at locally storing music nor relying only on data-driven streaming (in India at least).

Carl: Our users in India are very different from average users in India. Clearly over indexing on income, education and similarity to our users in US and Europe.

pankajparikhCan we expect the next #OnePlus to include a Type-C 3.1 with MHL Alternate Mode?

Aaron: I can't comment on future products but why do you want MHL over displayport over type C.

pheymanssWhat has been the hardest decision to justify to enthusiasts, and what has been the hardest to actually implement in your devices?

Carl: It's not about justifying, but learning together. The good thing with our users is that they'll always hold us accountable to our mistakes. An example is the whole debacle last year with NFC.

TehSViNHave any of you guys tried out ubuntu touch on the one plus one?

Carl: Tried it, but TBH it's not an operating logic I could get used to.

0912873465noAs someone who has been primarily an iOS guy, what is the biggest advantage for me if I switch to a OnePlus as opposed to a different Android product?

Carl: It's best if you can try different products and just get the one you like the most as there's no definite best smartphone. We all have different needs.

Wiz-1543A software OS question. Will OnePlus support other mobile OS like Ubuntu or Windows 10 in the future?

Aaron: No plans officially but you're welcome to port it. I have seen Ubuntu touch and sailfish running on devices unofficially.


OxygenOS, HydrogenOS and Their Unification

MikeyyL2304Can you tell us a little bit more about what's happening with Oxygen OS and Hydrogen OS right now?

Brian: We combined platform, system and framework already. Application layer is separated. So, global users will still have the Oxygen experience and users in China will have Hydrogen experience. Just to add to this, we invite you all to check out the latest Community Build for the OP3 here: http://ift.tt/2cX1zz7 . The 3.5.x Community Builds feature the merged platform, and you can see that it's still very much OxygenOS. We're also implementing a huge amount of community feedback, and we'd love to know what you think as well.

kira94By oxygen experience do you only mean the launcher or is the entire UI is going to be stock-ish as it is right now for the global users?

Brian: The entire UI will be stock-ish. We are just adding interesting and useful features on it.

harold_adminWill the stock Android aesthetic of Oxygen OS change? Is OnePlus developing a UI skin of their own? If so, what would be the main advantages of this skin over stock?

Omega: We will always stick to create a pure Android experience while at the same time adding some features that we believe will be very valuable for our users. You are always welcome to share with us your feedback.

2denggoodHow close to stock are you guys gonna keep the OxygenOS with the new staff?(hopefully it's stays close) How soon can we expect Android N?

Brian: We will stay close to stock Android experience. But we will have more useful features than stock.

DaveT1482If you are combining Hydrogen and Oxygen OS, will it be called H2OS and will there be themes to choose between the different styles?

Brian: No. Oxygen will keep its name and experience. We are not merging Hydrogen and Oxygen experience.

cyborg_2007What is the hardest part about developing a custom OS from AOSP? What is the OnePlus design philosophy when it comes to software?

Brian: The hardest part is not about developing the custom OS, it's improving whole experience.
This is a long story, but to make it short: We don't aim to completely WOW you. But after you experience Oxygen OS, we want you to think "Yeah, this is actually better than stock Android."

Omega: 1.The hardest part is how to build a stable and good performance platform, which we believe are fundamental and extremely important for our users. 2. Light, fast, stable, and closer to user need. That's why we keep rolling out community builds.
And thank you for your support.

_transienceHow do you plan on merging the Hydrogen and Oxygen? How will you satisfy "both worlds"?

Carl: Since the beginning, OxygenOS and HydrogenOS have had common code on framework and kernel levels, with the "merge", we're having them share more and more code on the Android and app levels too.
A good product is a good product no matter what part of the world you're in, we don't see it as two worlds. Some might have taken the community betas as an indication of future direction, whereas we've meant for it to be somewhere we can experiment and quickly react to user feedback. In fact, there's a new version coming in the next few days with many said changes.
As for updates, if there's any company feeling the pressure of needing to update fast, it's OnePlus. We have the most vocal and tech savvy user base, so this point is not lost on us. I believe that now, with our new software team structure, we'll be able to move a lot faster than before.

battler624Are you ever moving back to CM (probably with OP4?) or are you going to stick with Oxygen/Hydrogen and what is going to happen to these 2? will they merge completely?

Carl: So many things go on under the hood of OxygenOS. People seem to like it, but have difficulties pinpointing exactly what. It's important to control both the hardware and the software to deliver really good experiences, so we're not looking to outsource software in the future.
An example is the auto brightness. We used to ship with an off the shelf implementation that felt bad and we had a lot of feedback on this too. So we took some of the devices with the best auto brightness implementations and started measuring how they performed in different scenarios. Turned out it was very different than just a simple trigger. The end result that we shipped with the previous OTA fades dark very slowly and goes bright very quickly. This is only one of many things we modified to deliver a better auto brightness implementation. User feedback was very positive. We've got countless stories like this.

FullerphotoAnything exciting you can share about future builds?

Omega: Yeah so we have improved the power consumption. And we are also looking into the scrolling screenshot feature. Do you think it will be pretty cool?


Android Nougat and Updates

MehediHassanWhen do you guys plan on releasing it for the OP3?

Brian: We cannot share a timeline right now, but we are already actively working on it.
I want to clarify. The reason why we are unifying our teams, it's because we want to provide faster updates to our users. Some users have already seen our improvements through beta programs and OP3 OTAs. It's coming faster than before. This will carry over to the N update.

_kushagraBy the beta program you mean the community build right?

Brian: Yes. We have closed beta group and internal testing group as well. And everyone can join the open beta build(community build).

zingertek: When can we expect the changes in the 3.5 community build for the OP3 to be released as a regular OTA update?

Aaron: When it's ready, we are moving rapidly in the direction of stable.

xdarkpandax: You guys plan to update the software on the OP2 further?

Aaron: Nuget for OP2 is coming, had a meeting about it today.

vvarma1: Can you confirm whether Oneplus received early access to the android N source code before it was made available to everyone through aosp?

Aaron: I can confirm that nougat is chewy.

joddlarenHow do you plan to get on track with updates in the future?

Carl: Definitely, we've made software for less than two years and it's been a steep learning curve. To earn back trust we're adopting a show, don't tell strategy.

The_Otaku_GuyWill the OnePlus 2 get the OnePlus gallery and oneplus music apps?

Aaron: Yup as part of Oxygen 3.5 🙂

catalinthejoker10Do you have any eta on that ? or even a guess?

Aaron: You can try it today in the community build today. The community builds will be OTA'ed when we deem them stable.

EchoCorpIs there a way to block calls from certain numbers right now? If not, are there any plans on implementing that feature?

Aaron: It will be part of Oxygen 3.5+

vinicius97gAre you planning on releasing the tools necessary for Custom ROM devs to port features like Pocket Mode?

Aaron: http://ift.tt/2drSCxY and http://ift.tt/LEPE57 are all any rom developer should need be able to implment pocket mode there isnt much to it.

The_Otaku_GuyAny plan on providing Community Build updates to the OnePlus 2?

Aaron: We run community builds as needed. I'm sure a certain dessert in the future will come as a community build first.

Epix_XDWhen you release Nougat for oneplus 3, will you give additional features alongside the nougat features?

Aaron: Of course, we are shipping Oxygen not pure android. Oxygen has always been Android+ and will continue to be.

Nik3309Why can't you people provide proper updates at proper time like others phone companies?

Brian: That is what we have been trying to improve for last months. Unified platform, system and framework to speed up the update speed.


OnePlus 3 Bugs and Current Issues

onebusIs there going to be a fix for the GPS issues on the OP3? Am on 3.2.6, it's most stable for me when I switch to 2G. When on 3G/LTE…the blue dot on Google Maps is just constantly moving all over the place.

Aaron: First thing on me todo list for tomorrow.

Mossy375I'm not really sold on the 6gb of ram at the moment, as I often get app 'restarts' when selecting an app I opened 8 or 9 apps back. Are there any plans to make more use of the 6gb?

Omega: We have fully utilized 6GB. In terms of restarting problem, we need to identify the root cause – could be because the apps you are using consume too much memories in the background. Would be helpful if you can provide some of your most frequently used apps.

robotkoerWhy is Europe OP3 shipping time 5 weeks? I thought you got it under control by delaying a month?

Carl: We thought we would get it under control by stopping sales for a month. Just imagine the shipping time now if we didn't halt sales…
Although not the worst problem to have for OnePlus, we understand what unpleasant experience this could be for our potential customers.


OnePlus 3 Promises (Camera HAL)

gigatexCarl Pei tweeted an improvement to the camera experience on custom roms was being looked in to. Any news about that yet?

Carl: Camera team is still looking into how to do this the best way, and weighing the consequences in user experience.

yooouuri: When do you release the camera/hal sources?

Carl: Full unprotected source code? Never.
Something that community ROMs can use? We're discussing how to get it done.


OnePlus X and a Successor

chimnadoWill you ever release another 5″ phone?

Carl: Not looking that way. It's too hard to fit a big enough battery into a 5″ device.

harold_adminWhat does the future of OnePlus X software updates look like? Can we at least expect monthly security patches? Or even update till Oxygen OS 3.5 since that is based on Marshmallow?

Carl: The Android M OTA is coming next week!

[Author Note: The Marshmallow update is now live for the OnePlus X]


Dash Charging

CameraRickHow good it might be for the battery to be loaded that fast with Dash Charging – I imagine the degradation is a lot faster than with 'normal' charging speeds. Any comment on life expectancy?

Carl: We love Dash Charge too. This is a technology that has been thoroughly tested in large quantities in real life scenarios, and we don't foresee any problems. In fact, some may argue that it's even safer due to the 5 levels of security checks in addition to not having to charge overnight.

crispaperDo you have a power bank with Dash charge support in the works?

Carl: We were discussing this for the longest time, and we did a survey on our forums with a really positive response. However, we decided to shelve the idea as Dash Charge allows you to spend less time charging and we felt like carrying a power bank would be a bit counterintuitive to that.

aixnjLaptop with dash charging?

Aaron: Dash charge all the things

Bradon: Less time in the socket, more time in the pocket.™


Screen Protectors, Accessories and Ecosystem

CameraRickThere were some cropping issues with the official curved tempered glas as you will know. Is this adressed by now? And when will they finally be in stock again?

Carl: In regards to tempered glass screen protectors, the cropping issues you mention are necessitated by the curved design on the front of the phone. Any other configuration would have left air bubbles, or poor durability that couldn't pass our quality standards.

cdonald17Why isn't it possible to make the side bezels of the curved tempered glass thinner so no copping occurs? Or, why isn't it possible to create a curved tempered glass screen protector that is entirely clear glass (i.e., no black and white versions)?

Carl: Don't understand your first question. Second question is because it's very hard to guarantee that the user applies it 100% correctly. It's very likely for air bubbles to occur especially on the sides. Believe me when we've done a ton of experiments with every type of variation.

chronus_essI won't call screen cropping, and thereby reducing usable surface area of the phone screen as having passed any decent quality control, but I'm just a user, not a QA personnel.

Carl: Agree, thinking of killing the product line entirely. There's no perfect implementation on a curved surface with the technology we have available today.

TimonF1) In the EU Store why the cables for OP1 and OP2 nad their tempered glasses are not available to buy for at least 3 months now. 2) Why don't you make available for the Shop the googles for VR experience or the bags and other cool stuff you have?

Carl: 1) Because those products are getting old and we don't want to sit on inventory that we won't be able to sell
2) Loop VR was never a permanent product, and the backpacks are coming Soon™

highdiver_2000How is the OnePlus ecosystem coming along?

Carl: One step at a time. Over the past three years, we've shown that we can make good products and that we're here to stay. Hopefully the trust we've established will help us reach our next step easier, namely scale which (despite what some believe) always comes before building an ecosystem.


Forums and Feedback Reception

aashish_amberHow often do you guys look at the comments made by users on one plus forum about different bugs they face , do you have someone to note down those feedbacks and problems?

Carl: We have a whole team dedicated to this, and quality is something we take very seriously.
We don't only look at feedback on our forums, but also customer support, Reddit, other social media, email, etc. Every week, we have quality meetings where we go through the progress & priority of pending issues. If the issues are large enough, we'll block software (and hardware) from shipping before they're resolved.
Sometimes, it's hard to reproduce the issues unless you're in the same network conditions, so we actually have a globally scattered test team with people in all continents we cover. Once, we sent a test engineer to the home of one of our Swedish users to fully reproduce his issues.

Bradon: A lot of OnePlusers from several departments (marketing/product/customer service/platform/etc) spend a lot of time on our forums – myself included. Sometimes this is for feedback and bug report collection, and sometimes we're just hanging out. Since the beginning, we've always tried to break down that barrier between OnePlus and OnePlus users. The way we see it, we're tech enthusiasts, and we make the products that we ourselves want to use. You guys contribute tons of feedback and help to guide our brand and products. So, we're all part of the same community. This AMA is a small part of that overall mindset.
To answer your question more directly, though, yes. We collect a ton of feedback and bug reports, as Carl already explained pretty thoroughly. We also have something bigger in the works to make bug reporting even better.


Customer Service

MindstarxAre there any plans to improve your customer service?

Carl: Looking at our metrics, CS has been improving steadily over the past 3 years, but of course nowhere near where we want to have it and there will always be cases that fall through the cracks.


Carrier Exclusivity and Issues

K-NineHD: Will the O2 UK phone still have 2 Sims? Will the device be locked to O2? Will there be any O2 bloat installed? Will you let any carriers install bloat to the phone? Do you have any plans for expansion into more countrys?

Carl: Yes, No, No, No, Always looking to expand in the right way [Author note: Responses in order]

FettecheneyWhat is it like for you guys to try and work on compatibility with the different networks? (Verizon, T-mobile, etc) What makes it so difficult to get the phones to work with Sprint and Verizon's 4G networks?

Carl: Each carrier is different. Some have no proprietary requirements while some have lots and even have you pay them to help make sure that your device adhere to their requirements. Usually, the larger the carrier the more requirements.



The OnePlus Team did a good job at answering questions in the AMA, and it provided the perfect opportunity to glean more new information regarding existing products and future plans.



from xda-developers http://ift.tt/2cCIOjh
via IFTTT

Homescreen Critique 04

We have a fresh batch of amazing homescreen to go through in a new XDA TV video. Taylor continues to pick through user-submitted homescreens to find some of the most amazing designs. This is a great series to check out if you're looking for inspiration for your own homescreen setup. Also if you think your setup is already amazing, you can submit it for a chance to be featured in the next episode.

Check out the individual posts for the screens featured in this video, below.

vlcsnap-2016-09-28-09h27m56s879

Check out this homescreen here.

vlcsnap-2016-09-28-09h28m12s758

Check out this homescreen here.

vlcsnap-2016-09-28-09h29m02s120

Check out this homescreen here.

Submit your own homescreen in this thread to be featured in the next video.



from xda-developers http://ift.tt/2dttS7W
via IFTTT

Winners Announces for the Google Play Indie Games Festival

A couple of months ago, Google announced they would be hosting the first annual Google Play Indie Games Festival. The idea was to highlight some indie mobile game developers that have produced a great entertainment experience for mobile. There wasn't even a requirement that the game be available in the Play Store at the time of submission. Google just wanted to give some attention to game developers that deserved it and then reward them for their work.

At the end of last month, Google announced the 30 finalists who would go on to compete at an event held in San Francisco. At the time the finalists were first announced, only 10 of the games that were nominated were actually available in the Play Store. Now, 17 of the nominated games are currently available and more are confirmed to be released later in the year. So be sure to check out all of the nominees as each of them offer something unique to the mobile gaming experience.

The event in San Francisco was held on September 24th, and now Google has officially announced the winners of their first annual Google Play Indie Games Festival. Winners of the event were bit bit blocks, Numbo Jumbo, and Orbit. With finalist nominees also including Antihero (coming in 2016), Armajet (coming in 2016), Norman's Night In: The Cave (coming in 2016) and Parallyzed.

All finalist nominees received a combination of prizes that include Google I/O 2017 tickets, a Tango Development kit, Google Cloud credits, an NVIDIA Android TV & K1 tablet, and a Razer Forge TV bundle. Google has said they are bringing the Indie Games Contest to European countries next and will soon announce which countries will be eligible for the event. So be sure to prepare your best game to be entered as it could be a great opportunity to introduce your work to a worldwide audience!

Source: Android Developers Blog



from xda-developers http://ift.tt/2dkQVx1
via IFTTT

How to Discover Hidden Fastboot Commands

In my goal to discover as much about Android customization as I possibly could, I've made many obscure, yet interesting discoveries. I've shown you how to access hidden menus on your device by sifting through all of the hidden application activities on your phone. More recently, I've shown you how to access the hidden hardware diagnostic tool on certain smartphones. Now, I realize that some of you were disappointed in the fact that your smartphone was not covered in the previous article, and I apologize for that.

To make up for it, I'm going to walk you through something far, far more advanced and exciting: dumping your device's bootloader to discover hidden fastboot commands. This guide, although done on my Nexus 6P, is most definitely replicable on the majority of smartphones. However, what commands you will have access to will vary significantly between devices. Most commands will not really help you in any real situation, but nevertheless it's pretty interesting to dive this deep into your phone's settings. Let's get started.

Disclaimer: So long as you know what you're doing and can follow instructions appropriately, nothing bad should happen to your device. But, we are still messing around with our device partitions and the bootloader, so there is no telling what could happen if you enter the wrong command. Make sure you have an off-device backup ready!


Preparation

Before we get started, there's one really, really important thing to note. In order to extract your device's bootloader, you will need root access on your phone. If you do not have root access, you can continue reading this guide for educational purposes, but you will not be able to perform any of the necessary commands. Got that? Good. Another prerequisite you will need to meet is ensuring that your computer has all of the proper ADB/fastboot drivers. If you don't have the ADB/fastboot binaries, then I recommend installing Minimal ADB & Fastboot from our forums. As for the drivers, you can grab the necessary drivers for Google Nexus devices here and for all other devices from here. How do you know if you're good to go? Plug in your device, enable USB Debugging under Developer Settings, open up a command prompt, and type:

  adb devices  

adb-devices

If you see your device's serial number pop up, then you've got the right drivers.


Dumping the Bootloader

Our first step is to open a shell on our device so we can run commands over ADB. It's best that we run commands over ADB because we're much more prone to making mistakes when typing on a virtual keyboard, and making mistakes is not something you want to do here. The first command you should run in your command prompt is:

  adb shell  

If you see the command prompt change from displaying the ADB binary directory to showing the codename for your Android device, then you've successfully entered your device's local command line shell. Now, in order to access the partitions we need to dump, you will need superuser access. To do so, type the following:

  su  

The symbol in front of your device's codename should change from $ to # indicating that you can now run commands with elevated privileges. Be careful now!

adb-shell

Next, we will figure out the exact location of your device's bootloader image. In order to find the exact directory, we will print out a list of all of the partitions and their directories by name, and look for one in particular called 'aboot.' You will need to enter two commands as follows:

  cd /dev/block/bootdevice/by-name  ls -all  

adb-partitionsAs you can see above, a giant list of partition directories are printed out. These partitions are sorted by name, so we can easily discern the location of our bootloader partition. In my case, the bootloader, which is 'aboot' in the above image, can be found at /dev/block/mmcblk0p10. This will vary depending on your device, so it's important that you follow these instructions to figure out the true directory where your bootloader is located. Take note of this directory, however, as we will reference it in the following command to dump the bootloader:

  dd if=/dev/block/{YOUR ABOOT PARTITION} of=/sdcard/aboot.img  

adb-dump-bootloader

Once successful, you should find a file called 'aboot.img' located on the root of your internal storage. Now that we've dumped the bootloader, we need to examine it to determine what hidden commands we can find.


Hidden Fastboot Commands and their Uses

You might be familiar with some of the more common fastboot commands, such as fastboot flash or fastboot boot. There are many more fastboot commands as defined in the open source fastboot protocol. Here is a list of the fastboot commands available on every device with a bootloader based off of the latest AOSP code:

fastboot-aosp

What's missing in this list are fastboot oem commands. These commands are specific to Android device manufacturers, and there is no comprehensive list or documentation anywhere for what fastboot oem commands are available. Now, if your device manufacturer was kind enough to provide a fastboot command that lists all oem commands (try fastboot oem ? and see if that works), then you won't need to do anything further. If there isn't any command that prints a list of available fastboot oem commands, then you'll need to print a list of strings from the aboot.img and search for the oem commands manually.

'strings' is a linux command, the documentation for which is available here. As you can tell, I'm personally using a Windows machine, so instead I've been using a program that mimics 'strings' from Linux. The raw output of the 'strings' command on an aboot.img file will be quite messy, but if you simply CTRL+F for 'oem' you should find what you need. If you want to refine your search, you can try this command (for the Windows version I linked):

  strings * | findstr /i oem  

For the Nexus 6P, I compiled the following list of fastboot oem commands:

  fastboot oem unlock-go  fastboot oem frp-unlock  fastboot oem frp-erase  fastboot oem enable reduced-version  fastboot oem device-info  fastboot oem enable-charger-screen  fastboot oem disable-charger-screen  fastboot oem enable-bp-tools  fastboot oem disable-bp-tools  fastboot oem enable-hw-factory  fastboot oem disable-hw-factory  fastboot oem select-display-panel  fastboot oem off-mode-charge enable  fastboot oem off-mode-charge disable  fastboot oem ramdump enable  fastboot oem ramdump disable  fastboot oem uart enable  fastboot oem uart disable  fastboot oem hwdog certify begin  fastboot oem hwdog certify close  fastboot oem get-imei1  fastboot oem get-meid  fastboot oem get-sn  fastboot oem get-bsn  fastboot oem get_verify_boot_status  

Be warned that you should not attempt any of the above commands, or any of the commands that you discover on your device, unless you are willing to accept the risks. There is a reason these commands are hidden from the user.

That being said, I've thought of some neat uses for some of these fastboot commands I've found (that may or may not be present on your device, so follow the instructions above to check!) that should fancy the most hardcore Android enthusiast. There are two commands here that could have some practical use.

First up is the fastboot oem (enable|disable)-charger-screen command. What this does is disables the charging screen that pops up when your device is turned off. If you aren't a fan of the blinding brightness of the charging screen when your phone is off, then you can disable it via this hidden fastboot command!

Next, there's the fastboot oem off-mode-charge (enable|disable) command. This command determines whether or not your device will automatically turn on when a power source is detected. By default, it is set to 'disable.' I will admit that this command does not have much use for phones, but if you're planning on mounting your tablet into your car's dashboard, you will find this command incredibly useful. You will be able to set your device to immediately power on when the tablet receives power, such as when your car battery starts up. Conversely, it's quite easy to power down the tablet when power is lost by using an automation app such as Tasker. This command, by the way, works exactly as written on the Nexus 7 (2013).


That's it for this lesson in Android customizability. Share the commands that you discover (ideally in a pastebin link) in the comments below!

Thanks to XDA Senior Recognized Developer Dees_Troy for his assistance in the making of this article!



from xda-developers http://ift.tt/2df7f44
via IFTTT

Mozilla is Removing the Gecko Engine from Firefox OS

Firefox was first introduced back in 2012 and a lot of us here at XDA have had a soft spot for the platform. We are very passionate about open source software and Firefox OS offered a very open source mobile platform and it had some momentum for a while. By late 2014, 14 different carriers in over 25 countries around the world were offering smartphones that ran Firefox OS, but this didn't last very long.

Less than a year later, Mozilla had announced they would stop selling commercial Firefox OS smartphones. The company said they would discontinue the development of the platform for smartphones in May of this year. This was only for smartphones though, as in January of this year we saw Firefox OS being used in Panasonic 4K televisions. The company had thought that pivoting to connected devices was the way forward but even this didn't work out how Mozilla had wanted.

It's now been confirmed that development on Firefox OS has ceased so they can focus more on their browser, and the engine that runs it. In a Mozilla developer newsgroup, the company has announced they will pull all Firefox OS related code from the Gecko engine. The developers say this is needed in order to continue evolving the "underlying code that comprises Gecko" as it being attached to Firefox OS was hindering the development process.

While this isn't technically the end of Firefox OS as a whole, remember it's still an open source project, the community developers who are passionate about it can pick up where the project was abandoned. Mozilla says the community will need to fork Gecko and maintain the code base so that it is still compatible with Firefox OS. Time will tell if there will be enough people to not only start and complete the project, but also keep it going so that Firefox OS can continue on.

Source: Mozilla



from xda-developers http://ift.tt/2cVtTg6
via IFTTT

Replaced Galaxy Note 7 Reportedly Catches Fire

Samsung just hasn't had much luck with the Galaxy Note 7 this year, and this latest report suggests that things might not be changing anytime soon. Samsung has been dealing with their voluntary replacement program for the device since the start of this month. The South Korean conglomerate was hoping this program was all that they needed to do, but they were forced into doing an official recall just a couple of weeks ago.

It was estimated that this Galaxy Note 7 battery defect would cost the company upwards of $1 billion in parts and labor alone. This isn't even factoring in the negative perception the public has about the device after the scratch test, and even after the multiple fires that were started from the Note 7. A device that was called the best smartphone available today by many Android publications, and one that our own Daniel Marchena called a remarkable phone for life.

So Samsung has been replacing and refunding defective Galaxy Note 7 devices for a couple of weeks now. Just yesterday we talked about how replaced Galaxy Note 7 units were continuing to have battery issues. At the time, it was reported that some units were being charged while they were plugged in, while others were having overheating issues when the device was plugged in. Still, at that time there weren't any reports of replaced units catching fire or exploding. . .until now.

Hui Renjie is a 25-year-old from China who received a replacement Galaxy Note 7 Sunday afternoon that was delivered to him from the JD.com commerce website. Less than 24 hours after receiving the unit, the new Galaxy Note 7 reportedly caught fire and caused minor burns on a couple of his fingers while also burning his MacBook. The man says he has refused an additional replacement and simply does not trust the company anymore.

Samsung has received the defective unit and is currently examining the device to find out what happened.

Source: Bloomberg



from xda-developers http://ift.tt/2d4aage
via IFTTT