yashsingh1/xdaforums huggingface dataset:
[Amazon Fire Phone] gorilla p:
Yeah, I didn't think so. I looked into this and it looks like not all phones support IPv6 and I've been a bit spoiled with Nexus devices.

Either way, at least we know now.

---------- Post added at 06:15 PM ---------- Previous post was at 06:11 PM ----------

On a separate note, while I was at it, I took a look at the build.prop and it looks like there are a decent amount of optimizations in there, but I found a number of optimizations, including some T-Mobile specific optimizations that were not included.

These come from ROMs on my Nexus4, Nexus 5X, and the TMobile specific settings are from an XDA thread. I have all of the additional build.prop entries on my file repository

Bit.ly/makostuff.

I applied them to my buddies phone.

The one difference that I noticed was that it seemed to pick up a data connection a bit faster with the settings there (maybe coincidence) but either way, the phone had no problems with them.

http://pastebin.com/G5qQC3e9
[Amazon Fire Phone] KLit75:
Not sure if I missed the discussion but the proximity sensor is working very well now! Must be somewhat new because last time I tried it it failed (like 2 months ago.) I tried Gravity Screen and one I read about today called KinScreen. Both are doing what they're supposed to do. I think it's a really cool feature. I set it to sleep in pocket, sleep when face down, and sleep after 15 seconds if it is face up. Pick it up and it turns back on. This should help with saving battery and almost eliminate the need for the power button.

Further testing

Well gravity box works pretty well but noticed a huge battery drain. And after trying kinscreen awhile longer the phone started behaving strange (apps crashing, freezes). So maybe the sensor isnt quite ready. Improving though
[Amazon Fire Phone] themo44:
The 1/18 build drops calls frequently and SMS won't send and I have to restart the phone which allows me to do these two for a while before they stop working again
[Amazon Fire Phone] axel2230:
Did you notice anything different apart from the data connecting faster? I'm a T-Mobile user and I'd like to see if this could improve performance (my phone is performing well though so no complaints). I also noticed there are some qualcomm optimizations do they apply to our phone too?
[Amazon Fire Phone] gorilla p:
Yes, they're Qualcomm specific.

I don't have the phone so I didn't test 2d/3d video playback, GUI response times, etc.

But with this ROM, performance is excellent.

I even scaled back the CPU settings for improved battery life and its still really snappy.

Like I said, the settings didn't cause any problems and its a simple copy/paste.

I use FX File Xplorer (and root add-on) both on play store and 1mobile.

Open FX, open system (root), system folder, copy build.prop to another folder or rename for backup.

Open and paste lines at bottom.

They're all organized and labeled if you read the build.prop (they did a good job with that)

The entries that I've put together are organized as well.

If you look at the text file that I posted, it has an explanation for the TMobile tweaks at the bottom and a link to the post for more info.

Keep in mind, build.prop tweaks aren't magical miracle speed boosters (like some people have made their "UberSpeedSuperTweak mod" out to be). But often small improvements can be made.
[Amazon Fire Phone] axel2230:
Thanks for replying gorilla p, I already know how to add lines to build prop but I'm sure this will prove useful for others that may not know how to do this already. A thing to note though that this guide will also work with any root explorer app that also has some text editor for example: ES File Explorer, Solid Explorer, etc.

---------- Post added at 02:39 PM ---------- Previous post was at 02:10 PM ----------

#ggow is there a way to downgrade the boot.img just in case I run into an issue? This is the only phone I have that is working a 100% (except for the camera) with no stability issues and I can't afford to run into any major issues. Also what would happen if I updated the binaries but I didn't update to the latest version? (I'm on the 11/25/2015 build). What would happen if I did the opposite (update the rom but not the binaries)? Probably I'm being overly cautious here since there are some users complaining about connectivity issues, etc.
[Amazon Fire Phone] gorilla p:
Here is an updated pastebin file that people can just copy and paste.

I only included stuff that is not in there already and that has been tested.

I put the TMobile specific entries at the bottom so they can easily skip those if on another carrier. I think I saw some ATT specific ones as well. If so I will update

http://pastebin.com/SZV3bNm0

---------- Post added at 04:20 PM ---------- Previous post was at 04:01 PM ----------

Here are some ATT specific ones I found, but i don't have ATT and can't test

ro.ril.gprsclass=12

ro.ril.enable.3g.prefix=1

ro.ril.hsdpa.category=28

ro.ril.hsupa.category=9

ro.ril.hsxpa=3
[Amazon Fire Phone] KLit75:
Well i tried all the buildprop edits (including at&t). Phone booted fine, apps launched, performance, network speeds and mobile seem about the same. There was one glitch. About a minute after boot, my homescreen froze up. I couldnt scroll or launch apps (yet the clock still worked). Being impatient i was close to flashing my backup but it only lasted 30 seconds then everything was back to normal. So the at&t

tweaks seem safe. Im just not sure if they made a noticeable difference yet. But its really cool. Thanks for sharing! :)
[Amazon Fire Phone] Hackashaq:
Thanks gorilla p. I'm running the tweaks including AT&T on 2 phones without issue. No obvious performance change, but all working well.
[Amazon Fire Phone] Surmisation:
After much waiting, I finally liberated my Fire phone which for the most part is great!

I have noticed battery depleting steadily, whether on standby or in use. Could be from xposed??

In any event, over fireos, it's a huge improvement...

Many thanks!!!!
[Amazon Fire Phone] gorilla p:
I didn't try playing with xposed on here.

Check out BetterBatteryStats and WakeLockDetector and it may help you identify the issue.

I might try releasing a couple kernel setting profiles for this phone (max performance, balanced, battery saving). Many know how to adjust the settings themselves, but not all know what each setting does and the effect it has.

I've had a bit of success doing this on the N4/Mako and by playing with different settings, influenced some changes in default kernel configurations.

I only have access to this device every so often though as it isn't mine. I'll do it when I get a chance.

Check out the Optimal Battery Life document on bit.ly/makostuff. It's primarily for the Mako, but there's a good amount of universal info in there.
[Amazon Fire Phone] Savory_snax:
I had trouble with the 1-18-16 build and battery drain also. I went back to the 1-4-16 build for now. The 1-11-16 build is also probably OK.
[Amazon Fire Phone] Plonkplonk:
Last update didn't show any (new) problems for me. Battery drain is about 0.2-0.3 %/h overnight when phone is idle (with zooper widget and a weather widget on home screen).

Thomas
[Amazon Fire Phone] Surmisation:
Ha. Big bustle to format, flash, reinstall, reconfigure, re-authorize, re-download, etc.

Easier to just wait for the next build to ota & see if addressed. Battery drain is noticeable, but far from severe.
[Amazon Fire Phone] stunvn:
Hey guys I have a problem: can't send sms (Message not sent)

What should I do now? It happen since I update my phone to the latest version. Always happen at night. :(

I thought I can fix it by re-install, but it still the same.
[Amazon Fire Phone] zabihjan:
[emoji27] [emoji16] no such issue for me
[Amazon Fire Phone] Nobuddy0816:
I've also noticed a higher batterydrain with the latest release and went back to the release from Jan 11th.

The higher drain wasn'tn critical but notacible, so i decided to roll back and wait for the next release.
[Amazon Fire Phone] HForHacks:
The Fire phone's battery just outright suck. I maybe incorrect since I haven't used Fire OS since CM came out, but on standby for like an hour or two I look like two to three percent as well and sometimes more. I don't have much on my phone and I have applications like Clean Master that turns off applications and it doesn't even do much. You're not alone.
[Amazon Fire Phone] Surmisation:
My battery issue seems to have subsided some. Maybe because it was a fresh install??

I dunno too much about Android but windows indexes the drive after an install. That eats up lots of cpu cycles. Maybe a similar process?
[Amazon Fire Phone] ggow:
- I am not experiencing any battery drain issues at all, so...

- Can a few people experiencing battery drain use wakelock detector and/or GSam battery monitor to find out what is actually causing the battery drain - the more information that can be provided - the more I can help.
[Amazon Fire Phone] zabihjan:
[emoji27] [emoji45] [emoji16] what are you talking about. The battery life on my fire phone is top notch. What do you expect from a locked bootloader. You should be thankful you can use this sweet phone
[Amazon Fire Phone] Surmisation:
Sure. Just installed GSam...

As I mentioned, the slowly consistent sapping occurred initially but has subsided. The phone was reporting high usage for sandboxed chrome processes. I might surmise this is due to the difference in how chrome tabs are handled between LP vs KK.

I was coming from LP where clearing the multitask list also closed any open chrome tabs. But I'll report back with results from GSam.

None of this is complaints, just observations. I'm grateful for the work on this rom as I prefer the fp HW over any of my other devices. Great work ggow! Much appreciated...
[Amazon Fire Phone] :
Same here, aaayyyyy... :laugh: (with GAPPS, WhatsApp, Pushbullet and RSS Reader running... though I was mostly on WiFi and only little 3G / H+)
[Amazon Fire Phone] KLit75:
Can someone identify that top one (90%)

It drained my phone last night from 100 to around 48%. This happened last weekend and I naturally thought it was some buildprop tweaks i had just done. But since then I reverted the buildprop to original and even factory reset the phone.
[Amazon Fire Phone] ggow:
- Ironically that's a from the power driver in the kernel

- Not sure what's going on there - can you disable or kill it?
[Amazon Fire Phone] KLit75:
Im not sure either. I had gone into privacy and denied a few 3rd party apps access to waking up or set them to always ask.

No new apps, mods etc. In fact i had temporarily uninstalled/disabled the relatively new ones.

I DID misplace my stock charger and last night was the first time i used the alternate charger. Last weekend when it drained I purposely left it Unplugged to test battery. There it went from 100% to dead.

*How would i go about disabling it?

Whats weird is during the day under normal use, I have noticed a decline in battery but not concerning. The major leak SEEMS to happen when Im not using it.
[Amazon Fire Phone] ggow:
- I don't know if Wakelock Detector can be used to block the wakelock in question

- I think there are people here that are better versed on it use than myself
[Amazon Fire Phone] Surmisation:
According to GSam, the rogue process is:

system (dboxed_process#)

Fluctuates in amount of battery used. The # within the process name also appears to infrequently change.
[Amazon Fire Phone] adeebulrehman:
Did anyone try to replacing camera with Fire OS camera, and share the results.
[Amazon Fire Phone] :
This idea has been brought up a few times in the beginning, BUT:
[Amazon Fire Phone] ggow:
- I have no idea at the moment what that is

- Google search shows no useful information except other people were or are having the same issue
[Amazon Fire Phone] Surmisation:
Yep. Tried google and bing but nothing concrete.

In cm11's settings page, the process is displayed as com.android.chrome.sandbox.

I'm thinking the process name is shortened when populated in GSam and reports back the tail end of the entire process name xxxxxxxxxxxxxxxDBOXED_processx...

Again, I believe this goes back to chrome tabs staying open, even if chrone is cleared from multitasking in KK.
[Amazon Fire Phone] ggow:
- It might be worth trying an older version of chrome - if the problem has recently started occuring

- I'll check over any recent commits to WebView project too, just in case
[Amazon Fire Phone] adeebulrehman:
Need to play with camera.msm8974.so

Also below link might help, Any news please share.

http://xdaforums.com/showthread.php?t=2471900&page=3
[Amazon Fire Phone] gorilla p:
As you can see a few pages back, you may be on the wrong APN.

1 - Go to settings>select "Mobile Networks"

On a side-note, You can enable data roaming if your network doesnt charge for it. (many do not charge for it)

2 - select Access Point Names - Make sure the correct carrier is selected that you use.

I would recommend that everyone check this.

---------- Post added at 03:04 PM ---------- Previous post was at 02:40 PM ----------

I would try getting rid of Chrome and see if it helps. Maybe CM's Chromium will work better. or maybe get rid of Chrome altogether.

Greenify may also help, if you select Chrome to be Greenified. I always just assume that everyone is using Greenify, but looking in this section, people with this device might not be experienced Android users.

Just make sure to add Greenify to the "Device Administrator" list under settings>security.

Also enable Greenify option in settings>Accessibility

Another option would be to just ditch the google crap altogether. Its not needed, especially on this device, and even more so with a CM ROM.

You'd be amazed at how smooth devices run without Google crap, not to mention improved battery life.

1Mobile market is an excellent alternative to Google Play.

Firefox or Dolphin browser

OpenCamera

Waze Map (or MapQuest)

Google Drive can be used through ES file Explorer

Stock text messaging

stock keyboard

If anyone feels like giving it a try, wipe your device, just flash ROM and SuperSU (2.56 is latest system version). You can get supersu on bit.ly/makostuff. You can also get some other useful stuff there, including AdAway and Flash. Go to 1mobile website and download 1mobile app. I have yet to have trouble finding anything in 1mobile. It will update your apps like Plays tore does as well.
[Amazon Fire Phone] ggow:
New Build is Up

- Dated 26 Jan 2016

- Change log on Post #2
[Amazon Fire Phone] Plonkplonk:
So far no problems with the latest update. GREAT.
[Amazon Fire Phone] cthulhu1987:
So far the update looks OK, but I have irregular infrequent crashes.
[Amazon Fire Phone] Plonkplonk:
Are there different ways how apps can use the camera? Just now I found another app that can use it: Sun Surveyor is able to show a live view picture, while two qr-code readers I tried just can't.

Thomas
[Amazon Fire Phone] Surmisation:
New build is great!

I've been very careful to keep Chrome tabs closed. With 10 hours moderate use, battery is at 62%. Very happy :)
[Amazon Fire Phone] topcaser:
Hi, is it possible to configure the extra button's behaviour on the left hand side. In the keys section I can only select to wake up the phone and use it as music control

Gesendet von meinem Fire Phone mit Tapatalk
[Amazon Fire Phone] DNS_ERR:
Wow, this is great. I just upgraded my wife's phone with a July install with the 1-28 version - I did it dirty, didn't even wipe the Dalvik/Cache. I probably broke something but nothing's shown up yet!
[Amazon Fire Phone] ggow:
- Did you try wiping caches?

- Where are the crashes originating from and if they continue could you send me a logcat?
[Amazon Fire Phone] ggow:
- Yes, as well as the Standard Java interface

- External API's exist like OpenCV which may allow one to access the camera via C++
[Amazon Fire Phone] LilLowEK:
Very stable update. Ran it all day yesterday, no issues what so ever!
[Amazon Fire Phone] Surmisation:
Best build yet?
[Amazon Fire Phone] KLit75:
Thats a really tough question to answer, and for those who do you might get conflicting responses. My rule of thumb is always install the latest update. If a key feature isnt working, or there's an unusual amount of crashes then i revert back.

The 1/26 build is running fast and stable for me. Id say this rom has come a long way since july, and even then it was pretty impressive all things considered. But the biggest gains I think have come over the past month or so.
[Amazon Fire Phone] dato02:
ggow you decreased max stock clock speed?

edit: and now it's back on default again.

edit(2): is there a default occasion when system changes stock clock by itself, like when phone is getting too hot? i noticed that amps decrease when I'm charging the phone but never seen default clock change.
[Amazon Fire Phone] ggow:
- I didn't change anything like that

- The current release is a maintenance release

- The thermal engine will throttle or shutdown the phone if necessary
[Amazon Fire Phone] dato02:
and there are the screenshots. should've taken them the first time i saw it.
[Amazon Fire Phone] gorilla p:
This phone has a good amount of power. For most people, its far more than enough. I have this phone running Conservative governor, 384-1497MHz, 30 ramp down/90 ramp up, with 883mhz touchboost and GPU max freq was scaled down one level as well ( 300mhz?). This device still runs more than fast enough. Using that, Greenify and smart radio (switches data to 2G when screen is off, back to 4G when on). battery life has been significantly improved as well.

So for those that arent gaming or doing frequent multi-tasking, you can scale back settings quite a bit to improve battery life without causing lag. Conservative with 700-1000mhz touchboost is plenty snappy with a decently configured device.
[Amazon Fire Phone] dato02:
I'm not complaining about performance. it's just 25% freq decrease is just too much imo as of a device cooling side. i do know that 8xx series do that but didn't think it would go down this far. there are times when I'm gaming and charging at the same time and it takes ages for it to charge when I'm doing that. that mostly needs to be addressed by Qualcomm and OEM (amazon). Rom itself runs smoothly. don't have any speed tweaks or stuff like that. just gps conf and v4a (set at high).
[Amazon Fire Phone] llenp:
Workaround for Updating Encrypted Fire Phone

I just want to follow up on the encryption testing that took place about a month ago.

With an encrypted fire phone, It's still possible to do updates through safestrap recovery. (As some of you know, encrypting a phone makes the /data partition inaccessible in recovery.) The workaround involves having to sideload the .zip via the adb sideload feature. However, as of now, I can only dirty flash a new update. Wiping dalvik and cache is not possible if /data is inaccessible.

There's still the possibility of mounting an encrypted /data partition within recovery, but it involves some adb shell commands. I wasn't able to figure this out yet. It might just be the lack of proper utilities in the phone. I'll have to figure it out when I get a chance after work.
[Amazon Fire Phone] gorilla p:
You can expect thermal throttling on Snapdragon 800-810 CPUs.

Also gaming while charging will obviously take longer due to battery heat and battery use during charging.

This also has to do with your charger. If you're using the OEM charger you can expect that. Get a quality charger on Amazon from Anker, RAVPower or ChoeTech. They have smart chargers that can adjust power input and can increase input to charge while gaming. Your OEM charger will put out the same Amperage regardless of what device is connected and what it is doing.
[Amazon Fire Phone] cthulhu1987:
I'm not sure, where the crashes originate from and here's the logcat output.
[Amazon Fire Phone] DarthVesh:
just a heads up for this awesome ROM, i just found an app called 'Best HDR' in Google Play that seems to do a good job - i'm still testing it and it hasn't been updated for some time but it works. The only issue is switching between the front and rear cameras but its a matter of restarting the app so not a big deal IMO

https://play.google.com/store/apps/details?id=com.besthdr&hl=en
[Amazon Fire Phone] cthulhu1987:
Too dark.
[Amazon Fire Phone] KLit75:
Are you using a setcpu app to do this, or are you able to adjust them from settings then set on boot? I've always been nervous to try it--never touched the clock speeds without a custom kernel though now I'm learning it is possible.
[Amazon Fire Phone] gorilla p:
The best kernel management app available right now is Kernel Adiuter.

It works for just about every device and kernel and shows all available options.

It's entirely free and had set on boot option as well as ability to save profiles. Saving/exporting/importing profiles has been troublesome sometimes but saving them for your own use is no problem.

It's nice because you can setup a battery friendly configuration and save it

You can then setup a high performance/gaming configuration and save it.

So you can then use your battery friendly profile most of the time, but if you want to play games or do something resource intensive, switch to the performance/gaming profile temporarily without having to manually change all of the settings each time.

If you like, I could probably create a short video walkthrough if people can't figure it out.

The most important thing is knowing what each of the settings do.

Don't worry about lowering the max clock speed, I just wouldn't raise it very much (if its even possible). That won't effect anything. Just don't play with the voltages. Idk how forgiving those are on this device.

Go ahead and set conservative governor as well. If you don't notice any lag, then use that. It's a bit more battery friendly.

Also, this is technically a custom kernel that's included. CM has done a decent amount of work in adding tweaks and customization options. I was pleasantly surprised.
[Amazon Fire Phone] LilLowEK:
So far the build is solid. There was only one release I had crashes with. Battery is at 49% after 24 hours. This seems to be a constant improvement. Don;t get me wrong, it's always been good - just seems to be getting better for some reason. Could also be app updates.
[Amazon Fire Phone] gyannelis:
great job all around, I've been on this forum for months reading I just haven't sent a post before. Thank you for all the great work.

The only small issue I have is that after being on a call there is about a 30 second delay before you can make another call or before you can use data again...don't know why it does that, it has been like that since I've started using this rom back around November. I did notice a few others post about this issue, is there a resolution for it?

Thank you!
[Amazon Fire Phone] JDubbed:
How are you testing the battery? Are you fresh installing CM-11 and then just leaving the phone alone and checking on it every now and then? Is this from casual use? Heavy use? Or are you using a battery monitor app? Are there any 3rd party apps you have installed? Is your Google account connected to the phone? Wifi enabled? Details please! :good:
[Amazon Fire Phone] Angablade:
I've been on WiFi for 10 hours out of 17, watched over 5 hours of video, light gaming, lots of Facebook, and it lasted quite well. I've got my phone set to interactive with a range of 700mhz to 2ghz. I've got a script pack I created from personal code and some other public scripts and I seem to be chugging along okay. On most current build.
[Amazon Fire Phone] ferolac:
i don't no what happened but out of nowhere phone stopped detecting sim on its own. Tried restoring from backup no luck, tried clean installing the rom still sim not detected. The same sim card is working fine on the other two phones i have. Running 26-Jan build. please help!
[Amazon Fire Phone] ggow:
- Are the other two phones Fire Phones?

- Check it by reloading with FireOS

- If it doesn't work with FireOS then it could be a hardware fault