yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] :
Quote:

Originally Posted by Satras [MENTION=5749760]ggow[/MENTION]

Do you think there is time for some performance optimization?

Or is it as good as possible already?

Thanks

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1

Quote:

Originally Posted by djflaco908

I'll love to see more performance optimization out of this rom

[MENTION=5488402]Davey126[/MENTION] you wrote this to djflaco908 Remember?

Realize this is directed to [MENTION=5749760]ggow[/MENTION] but I'll add a bit of color. Spent some time over the past few weeks tinkering with various settings (because I like to play, not because I was dissatisfied) and came to the conclusion the defaults are well suited to this device...at least w.r.t items that can be tweaked via UI, apps and build.prop (governors, schedulers, caches, etc.) Ultimately the changes I made were related to personal preference and have little to do with the overall performance of the device. [MENTION=2907859]djflaco[/MENTION]908 - what areas are deficient? If you are looking for more "performance" there is only so much the hardware can deliver. CM itself is already well optimized.

You see [MENTION=5488402]Davey126[/MENTION], a little bit of your own meds. And I thought a private message is needed when its directly to someone? Nah

---------- Post added at 06:01 PM ---------- Previous post was at 05:54 PM ----------

Get that part of being busy working. But not the part where I'm told to private message someone for posting directly? Well I just proved wrong that half of these users post to someone directly without private messages. And why do I?
[Fire Original Android Development] DB126:
Of course you can do as you wish; it's a community forum to all to read and comment as they wish. Sorry you got all bothered.
[Fire Original Android Development] :
I didn't get bothered, simply I was trying to get my facts straight, that's all!

I manage to get back to cm this time without flashing previous builds but I had to start from scratch, I'll just dirty flash for now on. Is there anyway I can clean leftovers from dirty flashing?
[Fire Original Android Development] Signor Rossi:
Can we stick to the topic please?

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] :
Same thread,topic whatever you want to call it.
[Fire Original Android Development] ldeveraux:
For the love of Christ, this thread is about CM12. You want to pm a dev, go ahead. Just leave the other junk out of it until you lern teh netz. That's all we're asking of you...
[Fire Original Android Development] sd_shadow:
others will reply in a public thread, If you don't like it, use PM
[Fire Original Android Development] :
Since it keeps going, I never said I didn't like it, the other person said public thread OK well he didn't reply that to him self when he told the other person that the post was directly to the dev so why i couldn't I say the same?

---------- Post added at 08:23 PM ---------- Previous post was at 08:20 PM ----------

No disrespect but I'm not the one that keeps going on with it. I stopped I even posted how to clean left overs after dirty flashing and all I get is the same bull with the old post not related to the thread. And by the way you'll do the same if you was in my shoes.

---------- Post added at 08:25 PM ---------- Previous post was at 08:23 PM ----------

---------- Post added at 08:27 PM ---------- Previous post was at 08:25 PM ----------

Hi again, can someone please tell me how to delete leftovers after dirty flashing? I appreciate it
[Fire Original Android Development] fmc000:
Did almost the same (I never wipe caches, it's totally useless and if there are framework changes the optimization process will start anyway at the first reboot) but my Wi-Fi connection worked fine without needing a reboot.
[Fire Original Android Development] DB126:
Thoughts:

- may be true on this device (have not experimented to find out) but definitely needed flashing this rom on other Amazon devices such as HDX

- most common symptoms include hang on first boot (perpetual CM animation) followed by excessive boot time (many minutes)

- skipping wipes does shorten first startup time (sans framework changes) so if it works great!

- if you do experience a hang or other unexpected behavior might try a simple cache wipe before delving into more complex troubleshooting
[Fire Original Android Development] Franzferdinan51:
Tried this using flash fire and it failed had to use slim lp not bashing in any way just need to know how to make it work properly with flash fire I did same process as slimLP
[Fire Original Android Development] Shinyhead:
Just used flashfire to update to the latest CM build. No issues except all my apps got deleted... :(
[Fire Original Android Development] Franzferdinan51:
Huh weird I wonder why it failed for me maybe bad download on my side
[Fire Original Android Development] gregoriio01:
hi what happens is that I had a problem when trying to install cm 12.1 in my fire seven now stays in the logo of cm and nothing more there and I can not enter the recovery because I get apk factory mode and nose to do could help
[Fire Original Android Development] nicstoun:
Yotube 720?

How fix yotube app show 720? Now show only 480p.
[Fire Original Android Development] DB126:
No 720p option in overflow (3 dot) menu? Official YouTube app will only offer resolutions it thinks are serviceable based on connection quality/speed and other factors.

Have you tried streaming from a browser such as Chrome or Opera? Should see a HQ button which will switch to a higher bit rate if available. If the HQ button doesn't appear (or the video starts playing immediately) clear your cache or open the tab in a 'private' window.

I realize you were asking about the app but I sometimes have better luck streaming from YouTube's mobile site.
[Fire Original Android Development] nicstoun:
With Amazon rom i have 720p in quality menu.

So i think yotube not reorganize the device.

On same wifi with OnePlus i have 1080p, that is normal for device.

No with chrome and mobile yotube not have HQ button options.
[Fire Original Android Development] DB126:
Hum, not sure what the problem is. I have 720p option with generic CM 12.1 (2016012 build) on this device. Have not changed any identifiers in build.prop. Might be a regional thing.
[Fire Original Android Development] loocool2:
Edit: repeat answer.
[Fire Original Android Development] NeeKoNeeKo:
Just got my third(one dead no battery while bricked -.-) tablet today, still coming with stock 5.0.1

Installing CM was a breeze, thumbs up!!
[Fire Original Android Development] paula.eskaros:
flashed 12/1/2016 build today from stock using twrb everything stable and smoth but i can't fell any vibration and didn't know if the tablet even have vibration or not please help and tell me if i am missing something
[Fire Original Android Development] DB126:
No vibration; lacks hw support (you could have found this with a simple search)
[Fire Original Android Development] lazychai:
After flashed to CM12.1 via FlashLite, it stuck at CM boot logo and stock recovery not working. Please update once you got the solution.
[Fire Original Android Development] gregoriio01:
:confused::confused::confused:

---------- Post added at 11:46 PM ---------- Previous post was at 11:44 PM ----------

That same happens friend and if you know how to solve some let me know thanks
[Fire Original Android Development] andPS2:
hello [MENTION=5749760]ggow[/MENTION]

saw u were looking into fast charging with the fire hdx

can u look into it with the fire tablet and this rom as well?

i know u're pretty busy with all the roms (saw u did the fire

phone as well) though... ;)
[Fire Original Android Development] ggow:
- Fast charge needs a kernel mod to the power driver so can't be done at the moment as the bootloader is locked.
[Fire Original Android Development] f1ux:
I have just installed the latest version and also get the system UI crash when making a restricted profile.
[Fire Original Android Development] ggow:
- Seems to be a known CM-12.1 bug - happens on other devices too
[Fire Original Android Development] DB126:
As stock does not offer fast charging nor is it an advertised feature I suspect 5th gen Fires lack hardware support.
[Fire Original Android Development] paula.eskaros:
[MENTION=5749760]ggow[/MENTION] thank you so much for this amazing rom everything work more than I expected this tablet can do especially the battery life I got 6h sot over 2 days
[Fire Original Android Development] :
Thanks [MENTION=5749760]ggow[/MENTION] for your hard work for bringing this rom to fire tablets. Also It's working great with the maxxaudio sound mod I flashed no bugs to report has of now.

---------- Post added at 04:50 PM ---------- Previous post was at 04:32 PM ----------

Now I wanted to pick up 2 post that got my attention and that didn't receive any responses, the post was

1) clean leftovers after dirty flashing? Because I can't clean flash using flashfire, maybe its a known bug or something.

2)how can I flash the current build without having to flash previous builds like the other person mentioned?
[Fire Original Android Development] ggow:
- I don't know whats going wrong because no one has posted any logs to help determine that

- I dirty flash with flashfire and it seems to work fine here

- Is it working for anyone else?

- If not can someone post logs when flashfire fails?
[Fire Original Android Development] :
I think is a flash fire causing bootloops after installing the latest build.

There's a few post regarding people trying to flash the latest build and gets stuck on cm logo with no options besides going back to stock and starting all over again. The only way well in my case the only way I can be on the lastest build is to flash the previously build which is 20153012 then dirty flash the current as djflaco908 stated.

But again maybe its a flashfire issue not yours [MENTION=5749760]ggow[/MENTION] don't worry ;)

BTW cm is running smoothly with no issues, love the work.
[Fire Original Android Development] ggow:
Well at least there is a workaround. Will put a note on the FAQ about this
[Fire Original Android Development] :
I agree totally with you [MENTION=5749760]ggow[/MENTION], I didn't see it that way but now it made me feel much better that even though doing this workaround actually works and can have your latest build of cm using flash fire. Thanks again [MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] theophile2:
Shouldn't it be possible to build the module for the stock kernel and just insmod it?
[Fire Original Android Development] ggow:
- I may be wrong however on a really quick initial look

- As far as I'm aware the power driver for the ford device cannot be built as a module

- We could easily build a fastcharge module but ultimately that would only give us the the required SYSFS interface

- We would still need to tie that in with the actual kernel power module in order to control input charge current.

- Even if we were able to do this then we would still be limited to booting the stock kernel which means we would have two power drivers fighting each other

- It still leads back to one place which is we need an unlocked bootloader
[Fire Original Android Development] nujak:
I used flasfire to go from 12/16/15 build to the 1/12/16 build with no problems. I always setup Wipe (dalvik, system and cache), ROM, supersu and then nano gapps. Other then the first build, I've used flashfire everytime to install the new rom with no issues.
[Fire Original Android Development] ggow:
[MENTION=7216923](composer)[/MENTION]

- Perhaps you could try this
[Fire Original Android Development] ba6470:
Hello ggow,

thank you very much for your work.

I get a low budget tablet, with a high Class ROM

I would like to ask you if it would be possible to add the double tap to wake up function into your ROM ?

I have a One Plus One and use this option really often.

Thank you in Advance

Andreas
[Fire Original Android Development] ggow:
- We would need an unlocked bootloader for this to be added to the kernel
[Fire Original Android Development] :
That's more of the same situation as I was too, he basically flashed a previous build to get to the current. What I mean is flashing the current without the past build, now you get me? He flashed your previous build just like I did and then he updated to the current just like I did.

For example: when im coming from stock or different rom and when I try to flash the current build of cm that's where the problem is with flashfire, flashfire doesn't flash it just reboots the tablet to normal. And in order to get to the latest build I need to flash previous cm build to get to the current build.

---------- Post added at 12:29 PM ---------- Previous post was at 12:22 PM ----------

That's what i mean you still flashed over the previous build just like I did in order to get to the latest build. But try to flash the current build coming from stock or different rom
[Fire Original Android Development] ba6470:
Ohh i see, thank you !
[Fire Original Android Development] ggow:
- I'll try the latest build coming from FireOS
[Fire Original Android Development] CrazyDelta:
HI Guys,

Hope someone can advise. I went through all the steps of rooting my Amazon Fire 7 5th Gen (£35 version) using the SuperTool. It was rooted, then installed with FlashFire app. I provided instructions to Wipe and then install the CM12.1 rom and the Gapps. It went through the process and rebooted. But at the point that Chainfire screen comes up, and it is about to install Cm12.1, I get the following message - Can't install this package on top of incompatible data. It then boots up into the normal FireOS.

Please advise as I seem to be stuck at the moment. Thank you.
[Fire Original Android Development] gitchrodd:
After you select everything in flashfire you have to look and make sure it's doing everything in order. Most of the time I have to move wipe up the list to get the order correct.
[Fire Original Android Development] SWISHB2:
Hi

The same happened to me last night. I user Supersu to root device currently on Amazon Fire OS 5.1.1. I installed Flashfire using SuperSu successfully and then used this to flash CM12.1 and Stock Gapps. All seem to flash successfully but upon restart it boots up into the existing Fire OS. Someone please advise if you've had any success and how to install CM12.1. at the moment it seems only the Slim rom can be installed successfully.

Thanks
[Fire Original Android Development] CrazyDelta:
You are a legend, mate! Thank you. That was indeed the issue.

---------- Post added 20th January 2016 at 12:04 AM ---------- Previous post was 19th January 2016 at 11:40 PM ----------

I can also confirm that there is no 720p option in Youtube app after brand new clean install of latest CM 12.1. If it is a regional thing, just to let you know I am UK based.
[Fire Original Android Development] DB126:
Fascinating. Just reconfirmed CM build (20160112), YouTube app version (10.49.59) and availability of 720p. I do not have a G+, YouTube or Red account that might offer subscriber 'entitlements'. US based.

Other thoughts:

- flashed CM via TWRP along with latest GApps nano and SuperSU. Should not make a difference but maybe ...

- have a solid 5/30 Mbps connection and regularly see/exceed those speeds with low jitter (very fortunate!)

- Google/YouTube have a history of only offering resolutions considerable serviceable based on connection quality/speed and other factors. Not certain if that is still the case; algorithm might have some issues
[Fire Original Android Development] :
Nice question, I went and did some testing on ram expender from GP and the results was amazing. I converted 3gb and I bought nova 3 orbit and a couple of high end games that requires good hardware since those games doesn't run much on some low end devices so I did the test and the games runs smoothly with no issues at all. Imagine I tested it on my moto g and got a message saying this game isn't compatible with your device please request a refund. Now that message shows up on half of devices that I owned. <<bionicle>> test it for your self and you won't regret it.

FYI- yes ram expander does work
[Fire Original Android Development] glate:
Saw this and figured I'd throw my details in in case it's helpful.

Using this video - https://youtu.be/ZIM1HydF9UA

1. I get offered 1080p on desktop and my CM 12.1 nightly hltetmo.

2. 480p offered on my Fire (20160102 dirty flash via TWRP) DPI is 213.

All devices are connected using the same WiFi. Fire actually shows faster WiFi connection 65Mbps (2.4GHz) compared to 19Mbps (5GHz) for my Note.

I have a solid 5/115 Mbps connection so I don't think it's bw related.
[Fire Original Android Development] DB126:
Quick test to verify discrepancy is not content related ...

- 720p on 2015 Fire (20160112 dirty flash via TWRP; caches wiped)

- browser (Opera 34) displays HQ toggle

Neglected to mention in previous post: device set for default DPI (160).
[Fire Original Android Development] qtotter:
Install just open gapps pico or nano or mini with FlashFire on FireOS, and let it reboot. Then, install cm12.1/SuperSU/gapps with FlashFire.
[Fire Original Android Development] loocool2:
:confused::confused:I have a flashing red border around chrome dev when I open it, and when it seems to be using a lot of RAM; and disabled strict mode, but there's still a flashing red border. I didn't add lines to build.prop so to not mess up my device, and I am wondering if this can be fixed. I've seen this problem in other forums, but none of the solutions seem to work. Is this a cm problem or something else?
[Fire Original Android Development] ggow:
- Try adding these two lines to the build.prop

- Worked for me a while back when I had the problem on another device

persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
[Fire Original Android Development] BR3W CITY:
I had no problem using TWRP to flash CM12.1 and Gapps pico, and it boots up and functions pretty much correctly....but at random intervals (sometimes 2 seconds, sometimes 2 minutes) it prompts the android.process.acore has stopped error. I can OK it and continue to run apps/etc, but its frequency prevents most things from really working as it interrupts. Tried to wipe and flash again, no change. (I started with 5.01, and did have the Slim rom working before as well).
[Fire Original Android Development] ggow:
- Never seen that issue myself

- Anyone else?
[Fire Original Android Development] ggow:
New Build is Up

- Dated 20 Jan 2016

- Change log on Post #2
[Fire Original Android Development] PesSarmiento:
Never
[Fire Original Android Development] glate:
Installed via TWRP. If there's anything you'd like tested please let me know. No noticeable differences from previous build at first glance.
[Fire Original Android Development] :
hi, after trying to flash today build i ended up with no stock recovery and stuck on cm logo and with the only option fastboot, is there any workaround this? i used flashfire
[Fire Original Android Development] DB126:
No workaround (assuming 5.1.1 bootloader); device is soft-bricked.
[Fire Original Android Development] sd_shadow:
send it back to Amazon for a one-time free exchange.
[Fire Original Android Development] :
thats it no commands to fastboot? men that sucks really i shouldnt put wipe first like 1 person discribed
[Fire Original Android Development] sd_shadow:
yes wipe needs to be first
[Fire Original Android Development] :
soft brick and not hard bricked? so theres hope if theres a workaround in the future?
[Fire Original Android Development] sd_shadow:
bricked until someone finds a way to unlock the bootloader, which could be never, or tomorrow
[Fire Original Android Development] glate:
Worth adding a FlashFire section the the FAQ? Seems like setting the order is very important.
[Fire Original Android Development] :
dam that totally a doom. will asking amzn to replace cause my account to close?
[Fire Original Android Development] DB126:
Nope. Generally no questions asked on first (and only) complementary exchange.
[Fire Original Android Development] ggow:
- When you get you're new device, do not let it update the firmware automatically

- Stay on 5.0.1 and you'll have TWRP access
[Fire Original Android Development] :
thanks [MENTION=5749760]ggow[/MENTION], is there any chance booting up the os with sd card works? Like some other device does when this paticular problem happens?
[Fire Original Android Development] devlspawn:
Don't know why people are telling you there is no workaround. Just go into boot options (volume down + power) and choose adb load. Then run:

adb sideload update-kindle-global-37.5.4.1_user_541112720.bin

Get update-kindle-global-37.5.4.1_user_541112720.bin stock 5.1.1 image from amazon.
[Fire Original Android Development] sd_shadow:
I don't know why you can't read

They cannot boot to recovery
[Fire Original Android Development] :
lol. Hey amzn is sending ups to pick up the fire for service, will they know i had a custom rom and not send me a exchange afterwords? S*** i told them the tab is no longer booting to recovery and they made a service repair status.
[Fire Original Android Development] DB126:
Seriously? Yes - the regular contributors here are all hapless fools who can not figure out the bloody obvious. Thanks for stopping by.
[Fire Original Android Development] sd_shadow:
Amazon doesn't seem to care, and should replace without a fuss
[Fire Original Android Development] gitchrodd:
I think I have a work around.

At least this worked for me. Using rootjunky tool kit. I put fire in fastboot mode. I plugged my PHONE (nexus 6) into computer. Choose the option for reboot into twrp in tool. Waited tell phone rebooted to fastboot. I unpluged and plugged in fire. It booted into twrp. I was bricked couldn't get adb to recognize device at all.
[Fire Original Android Development] DB126:
Most returns are probably re-imaged and sold as refurbs (like the one you'll be getting). I suspect a small sampling are examined further to look for common failure points and gain some insight on what folks are doing in the wild.
[Fire Original Android Development] sd_shadow:
right, there is nothing wrong with them, amazon just hasn't released the image files needed to fix it ourselves.
[Fire Original Android Development] :
ok sounds good. i know what was the cause of everything already after looking on your page

- THIS IS WHAT I DID, WIPE/FLASH ROM/SUPERSU/GAPPS

now i know after selecting wipe as first it will be at the buttom after selecting the others to flash, so it looked like this before hitting flash- ROM/SUPERSU/GAPPS/WIPE. but my dumb a** dragged wipe to the top of the order and when i hit flash it was stuck on wiping..........and patching image... so that was the problem it wiped the stock recovery. so now i know why people had no way getting stock recovery. but hey the world didnt end to learn a lesson.

---------- Post added at 10:43 PM ---------- Previous post was at 10:01 PM ----------

was you able to recover the fire after doing your workaround and was you on 5.1.1 when you did it? sounds interesting
[Fire Original Android Development] gitchrodd:
Yes this worked for me. I was in boot loop after trying to flashfire from another rom. Was unable to get into anything but fastboot but could not connect with adb. I was able to get into twrp and wipe/flash and it was unbricked. But I'm not on 5.1.1.

Plus it's worth a shot. What the worst that could happen?? Besides bricking your phone because you tried to fastboot boot the wrong recovery..... So that whole disclaimer blah if you do try
[Fire Original Android Development] jedpublic:
I installed cm-12.1-20151222-UNOFFICIAL-ford.zip with FlashFire without issue. Today, I'm trying to update to cm-12.1-20160120-UNOFFICIAL-ford.zip. FlashFire will load and then there is a quick blip stating that it's flashing the zip and then it just reboots back into 20151222. Thoughts?
[Fire Original Android Development] sd_shadow:
fastboot doesn't work with 5.1.1, that why they are using FlashFire
[Fire Original Android Development] gitchrodd:
My bad. Since I'm not stuck with 5.1.1 I misunderstood and was under the impression you couldn't use adb fastboot. Sorry