yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] sd_shadow:
custom Recovery, custom kernels....
[Fire Original Android Development] :
Because its marshmallow? Mmm a question with a other question lol, fireos is 5.1.1 so thats lollipop 5.1.1?

---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------

Oh ok , so custom kernel speaking in general has to do with overclocked or a custom kernel doesn't officially stands for a overclocked kernel? Just asking I thought custom kernel was only to overclock lol
[Fire Original Android Development] DB126:
Salvage bricked device...
[Fire Original Android Development] sd_shadow:
http://xdaforums.com/showthread.php?t=3210485

[Index]Amazon Fire 7" - 5th Gen-2015

https://en.m.wikipedia.org/wiki/CyanogenMod#Cyanogenmod_13

kernels effect much more than that.

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

http://xdaforums.com/wiki/ROM-VS-Kernel#The_kernel
[Fire Original Android Development] ggow:
- I've located the cause to be a proprietary library

- Still looking into a fix
[Fire Original Android Development] Signor Rossi:
[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
[Fire Original Android Development] :
I'll love to see more performance optimization out of this rom
[Fire Original Android Development] ggow:
- Already looking into this

- I have some framework changes which I need to finish
[Fire Original Android Development] DB126:
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=7173628]djflaco908[/MENTION] - 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.
[Fire Original Android Development] :
Hey [MENTION=5749760]ggow[/MENTION] do you have any plans in the future to make cm12.1 more like cm13 like features or more powerful features to the cm.12 without needing 3party apps

---------- Post added at 10:16 PM ---------- Previous post was at 10:11 PM ----------

I know the question was for the developer but it doesn't hurt to go along with it. 2 is better than 1, I think so. Second in my opinion cm12.1 is well stable I was thinking maybe hmm add hardcore feature to the ROM instead of using 3party apps as I already mention directly to developer [MENTION=5749760]ggow[/MENTION] to the post

Like for example, have its own taste and features only [MENTION=5749760]ggow[/MENTION] and cm can deliver. Not wanted to go around testing other ROMs because of optimization or because of speedy. I love cm its called " GIVING IDEAS" ideas don't bother nobody, and pretty sure it doesn't hurt to ask, but ideas darn sure opens doors for the future.;)
[Fire Original Android Development] DB126:
Ok, fine. You'll get your answer soon enough. Guessing it will be along the lines of stock CM12.1 with only those modifications necessary to insure compatibility/stability on a specific HW platform. Personally I want CM to look/feel like CM ... not someone's interpretation of CM. Love the variety of ROMs available for various devices; each should have its own name/identity to distinguish it from the rest.

Who knows, maybe [MENTION=5749760]ggow[/MENTION] will develop a super CM (under a different name) that is more to your liking :)
[Fire Original Android Development] :
[MENTION=5488402]Davey126[/MENTION] lol maybe hope to see a other ROM by [MENTION=5749760]ggow[/MENTION] since hes a good dev always hearing feedbacks from people and trying to help those running with issues like I had before. Super cm? Now that doesn't sound bad at all. I don't expect a respond from ggow. as other person already asked for more optimization but hey atleast I tried. Hey [MENTION=5488402]Davey126[/MENTION] why don't you make your ROM?
[Fire Original Android Development] DB126:
LOL! [MENTION=5749760]ggow[/MENTION] roms suit me just fine. I only build/tweak when absolutely necessary.
[Fire Original Android Development] :
Oh so your a developer your self? Wow I feel stupid
[Fire Original Android Development] DB126:
Yes but on other platforms. Android is just a hobby.

Moving on; others don't need/want to see this personal banter. :)
[Fire Original Android Development] :
That's great to hear really.

Yeah before someone comes saying this is isn't part of cm so take it somewhere else blah blah blah lol. Actually that happend to on a droid 2 thread like 4yrs ago. OK back to cm, yes in think there should be a fix upon flashing cm12 updates without me have to flash pico gapps in order to flash ROM
[Fire Original Android Development] kingrat:
If I can bother you guys going back and forth over nothing

is there a preferred way to upgrade this rom?
[Fire Original Android Development] :
Obviously is something

You mean flash the latest built?

If you are talking about flashing the latest built then you can just flash it like any other rom. But if you tried flashing and it didn't go through the only way that worked for me was flashing pico gapps first and reboot the tablet then flash ROM and SuperSU,mini gapps. That's if your on cm built now if your coming out of other ROM and you flash this ROM with fire flash like I did you get a bootloop but that's only some cases like mine as happened
[Fire Original Android Development] DB126:
lol :)

I am fortunate to have retained the 5.0.1 bootloader so just dirty flash via TWRP (plus GApps and SuperSU for good measure). Typically flush caches before rebooting. Some have experienced problems with this approach and other dirty/clean flashes when overlaying CM or another ROM. Best to read up on their experiences and suggested mitigations.

Thoughts:

- always backup up existing rom if you have that option

- flush caches before/after flashing (or "factory reset" in TWRP if you don't care about data/apps)

- try a clean install if dirty flash fails

- if everything is working now don't bother upgrading (if it ain't broken ...)
[Fire Original Android Development] ggow:
- No plans to make cm-12.1 like cm-13.0

- cm-12.1 is cm-12.1 :)
[Fire Original Android Development] newsera:
Any way to fix the low call volume during loudspeaker calls over Facebook Messenger? Anyone else experiencing it?
[Fire Original Android Development] glate:
[MENTION=2914987]kingrat[/MENTION] if you have access to TWRP that is the preferred method of upgrading. You can do a dirty flash (upgrade rom then clear cache/davlik) unless it's specified in the first couple posts by [MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] darkgiant:
Can someone help me here: I currently have Fire OS 5.1.1 and have my device rooted and have FlashFire installed, but I am having insane amounts of trouble trying to install CM onto this device, is there a proper way to do so with 5.1.1 that someone can please explain how to do so?
[Fire Original Android Development] DB126:
Info in this thread is not helpful?

http://xdaforums.com/showthread.php?t=3269839
[Fire Original Android Development] kingrat:
Thanks for all the responses. Yes I have access to TWRP - and I have dirty flashed one before and it worked fine but didn't know if that was the preferred method.

Everything working well, thanks for all of your hardwork guys
[Fire Original Android Development] glate:
Not sure if it was user error or bugs in FlashFire but there have been a number of issues reported throughout this thread related to it. Good old fashioned TWRP is the only way I'd ever recommend (where possible obviously).
[Fire Original Android Development] ggow:
New Build is Up

- Dated 12 Jan 2016

- Change log on Post #2

- Still looking into EGL error and other small issues
[Fire Original Android Development] ggow:
- There is no platform.xml

- I don't know if bitbucket is better - I just prefer it.

sidenote: Been really busy at work, hopefully get a new release out soon with some more fixes.
[Fire Original Android Development] kenokech2:
Yes I saw the new commits on the other cm 12.1 branch and wanted to test the fixes out. But thanks anyway
[Fire Original Android Development] shiz0id:
Just wanted to ask if device encryption works since this is a custom ROM
[Fire Original Android Development] niphoet:
Probably not since the boot loader is still locked.
[Fire Original Android Development] shiz0id:
Thanks, I was so close to doing this last night, but then I thought I better ask.
[Fire Original Android Development] ggow:
- I have tested the encrypt feature and it does seem to work.
[Fire Original Android Development] shiz0id:
Will this work on the tethered build? I probably won't flash a new image unless I have to.
[Fire Original Android Development] ggow:
- Yes it will, I tested it on that same build.

- I would urge you to upgrade to the untethered build

- it will make it easier when the tablet reboots to do the encryption
[Fire Original Android Development] shiz0id:
Appreciate it, on another topic, do you think the Fire will get a Marshmallow ROM if we unlock the bootloader?
[Fire Original Android Development] ggow:
Yes there is a good chance if we unlock the bootloader and can obtain compatible binaries.
[Fire Original Android Development] Awesomeslayerg:
Theres also a little lag between when you rotate it, wpmdering if its possible to increase it? I can also post logcats of the bluetppth if needed
[Fire Original Android Development] ggow:
I am looking into Bluetooth at the moment.
[Fire Original Android Development] Awesomeslayerg:
Heres my logcat

Put it in a zip file because it was to big to attach it
[Fire Original Android Development] blueberry.sky:
Can we continue to use the current untethered boot method for Marshmallow (w/ locked bootloader)? Where could the binaries be found if amazon doesn't release a marshmallow fire OS update?
[Fire Original Android Development] omnikai:
Anyone having problems with hardware accelerated video? VLC, Dice Player and Plex all just lock up for 10 seconds and play nothing but audio when playing back simple m4v files. Switching VLC to software mode works (disabling hardware acceleration. Netflix doesn't work either.

Netflix works, though it takes a few seconds for the video to start playing.

Edit: Ah, it does sometimes eventually start playing after 15 seconds or so, but often at subpar framerates. Probably related to the previously mentioned gpu bug.

Great work overall though. It's already a much better tablet with CM.
[Fire Original Android Development] gram117:
Can you add the performance options like on stock cm12?
[Fire Original Android Development] ggow:
- I'll look into it

EDIT:

- It doesn't seem to exist anymore

- I have Kernel Adiutor installed and does the job nicely
[Fire Original Android Development] csolanol:
Hi [MENTION=5749760]ggow[/MENTION] , as amazon didn't provide a valid power_profile.xml file in stock firmware I have adapted one for this device and looks like it is working after some days of test. You can get it to fix battery stats in the device tree on my github.

Enviado desde mi KFFOWI mediante Tapatalk
[Fire Original Android Development] archerymodz:
Great job with this ROM, I'm not noticing any major issues. In the mean time while battery stats don't work y'all can use wake lock detector from the app store, it provides a lot of details.
[Fire Original Android Development] sd_shadow:
Yes, there is see How to install CM12 1 on the Amazon Fire 5th gen Tablet by [MENTION=4246643]Tomsgt[/MENTION] (Rootjunky.com)

[YOUTUBE]4dwguHoxTvo[/YOUTUBE]
[Fire Original Android Development] darkgiant:
No - because FlashFire doesn't like the CM12 ROM, it said it was incompatible during the flashing process. I gave up and went ahead with SlimLP.
[Fire Original Android Development] ggow:
- It works with FlashFire from since 4 versions ago
[Fire Original Android Development] glate:
New build flashed via TWRP. I don't have any issues with the previous build but wanted to comment to say that this build appears to run smoothly and flashed cleanly.

Question: is the "Android security patch level" from the Amazon boot.img I assume? That's the only explanation I could think of as to why it's so much older than my other CM device.
[Fire Original Android Development] sam tyler:
[MENTION=5749760]ggow[/MENTION] hold up with the updates!! I only put the 4/1/2016 update on my fire yesterday!! back to salt mine comp......:thumbup:
[Fire Original Android Development] der-mali:
Build 12-01-2016 runs very smoothly!

Just recommend to flash current opengapps.org as of 09-01-2016

(if you use Gapps at all).

***

Q: do we really need these four system apps?

- messaging services

- mobile data

- mobile network configuration

- phone

or can we simply delete them?

Can we take it out in the next build?
[Fire Original Android Development] DB126:
- most are needed (eg: mobile data & network configuration play into WiFi)

- not a fan of adding/deleting standard components from 'builds' unless essential for stability/functionality. User can tweak if desired.
[Fire Original Android Development] ggow:
- I won't be removing them because they are required
[Fire Original Android Development] ggow:
- My understanding is you can look up the date stated by the Android security patch level on Google vulnerability list and see at that date which vulnerabilities you are protected against.

- The date is not related to the boot.img
[Fire Original Android Development] glate:
My hltetmo on CM shows Jan 1, 2016 and I noticed in the changelog for SlimLP showed that they were updating to January as well which made me curious as to how that all worked. I suppose it just depends on where the priorities for each individual ROM are and how much help the devs have at their disposal?

Thanks again for all your hard work [MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] williamvito:
Updated the ROM today without issue and everything functionality wise is running smooth, still running into the issue of when I move apps to the SD card they are gone after reboot, have formatted my existing card and tried a new one without success. Still not knowledgeable about running a remount script which was mentioned a few pages back so I guess my questions are is a remount script able to be done from the tablet itself and is it a permanent fix? I appreciate all the hard work done thus far with the builds and look forward to a response.
[Fire Original Android Development] Deuces:
wifi problems with dirty flash from 20160104 to 20160112. will not connect to wifi

removed ssid, re-added, still broke. removed ssid, disabled wifi, enabled wifi, added ssid, still broke

restored to 20160104, all fine.

if i'm the only one i'll wait til next release and try again. i'll wipe if it's still broken
[Fire Original Android Development] atayal:
can we flashfire from Slim (2.3) -> CM 12.1 (jan 12)??
[Fire Original Android Development] DB126:
Curious if you rebooted between testing events. WiFi on HDX (thor) occasionally exhibits the same behavior. Reboot usually fixes it.
[Fire Original Android Development] nirogu325:
You can always try and delete those and see if something goes wrong or not. I did delete those and it's still rock stable (Wi-Fi works) but please note I'm not running CM but SlimLP so your mileage may vary.

---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------

Either what was suggested above (a simple reboot) or a clean flash. I never dirty flash and it's because the easy way isn't always the best.
[Fire Original Android Development] Signor Rossi:
I just realized that I got this too.

Quick way to repair this (temporarily?) is to goto settings => apps =>swipe to on sd card, select a small app from that list and click move to tablet.

This made all my apps on the SD card magically appear again

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] Doggy77:
I just updated from 20151222 (with GAPPS nano) to 20160112. Everthing works fine but one question How can I get rid of the GAPPS?

I used "Flashfire", wiped with all check boxes marked (system, 3rdparty, dalvik, internal and cache) and flashed the ROM.ZIP and the SuperSu.ZIP (and made sure to wipe before flashing).

After the reboot I noticed that the old GAPPS are still installed? How can i get rid of it / perform a real clean flash?

Best regards,

Markus (Doggy77)
[Fire Original Android Development] DB126:
- dirty flashed via twrp over 20151216 along with SuperSU 2.46 and Open GAaps nano

- wiped cache and dalvik (only)

- everything went as expected

- experienced WiFi startup issue reported by [MENTION=1812777]Deuces[/MENTION]; reboot resolved it (as expected)

Reporting as FYI to others - especially second reboot after dirty flash/upgrade - good practice on any platform.
[Fire Original Android Development] :
Can someone confirm using ram expender app works on this ROM? I activated ram expender and I swapped 2gb and I see 3gb in total and to confirm i downloaded a other app and I do see that 2gb is active but I want to know if its true with this ROM or kernel?

---------- Post added at 10:01 PM ---------- Previous post was at 09:20 PM ----------

Also I just dirty flash from 20160104 to 201600112 and everything is running smooth and I didn't have any issue flashing through flashfire.

Still have supersu,gapps,apps,wifi pw, and everything I putted on besides nova launcher but doesn't hurt to redownload it. Good job [MENTION=5749760]ggow[/MENTION] I also didn't run into the problem where flashfire didn't want to flash built 20151229 and 20160104.:good:
[Fire Original Android Development] Signor Rossi:
[MENTION=5749760]ggow[/MENTION]

Not sure if it's due to the latest build, but IPTV using Kodi works most of the times fine now

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] der-mali:
To get rid off GApps you need to do a factory data reset.

I guess there is no other way.

Additionally you can do the wipe in recovery mode.

-> Settings

(System)

-> Backup & Reset

-> Factory data reset

-> RESET TABLET

Don't select "Erase stored content" if you want to keep pics, docs, downloads etc.
[Fire Original Android Development] qtotter:
Try "forceclean" option?

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[Fire Original Android Development] loocool2:
[MENTION=5749760]ggow[/MENTION]

Looks like the android security patch level is outdated, (still on 12/1/15) and there were a few critical patches, looking at the changelog from the (1/1/16) update. Could you update it sometime, thanks for this great Rom!
[Fire Original Android Development] lazychai:
Hi, i'm having 5.1.1 and bootloader is locked. Any method that I can flash to this ROM without CM or TWRP recovery?
[Fire Original Android Development] HA4ever:
Search before you post.. Your question has been answered more than once
[Fire Original Android Development] Doggy77:
Thank you for your hint. I do not have any important files on the tablet (it is just "for playing" at the moment), so I wiped all except the external SD-card. It worked (mostly). The PlayStore is still installed, but the other apps&widgets have disappeared. Also the "SuperSu" remained installed.

For me it is perfectly fine.

Best regards,

Markus
[Fire Original Android Development] DB126:
Bootloader is locked on every 2015 Fire regardless of OS version. Being able to boot a custom recovery (CM or TWRP) does not equate to an unlocked bootloader. Search for response to your rom question (yes - you can).
[Fire Original Android Development] :
Sorry [MENTION=5749760]ggow[/MENTION] but I can't keep flashing previous builts to get to the current built. Dirty flashing worked but then noticed performance issues. So decided to wipe everything and reflash the current built and nothing same old thing with flashfire not flashing nothing. Lucky I had a copy of built 20151230 then flashed it with the next built then the current built and I don't think doing this is normal just to be on the current built and also flashing pico gapps to get into the next builts also is not the right thing to do. Have no choice just to stay away from cm till its fixed. Oh also I forgot to mention that coming from any other ROM while trying to install cm I get stuck on flashing, this only happens when flashing cm coming from elsewhere.
[Fire Original Android Development] DB126:
It's great to have choices! Take a stroll over to the SlimLP thread to see if that works better for you. Dirty updates work great for many (self included) especially those able to boot TWRP. Flashfire is a different beast and seems to present problems for some migrating from/to other roms. I am sure it will get sorted in time but for now SlimLP *may* be a better option for frequent updaters.

BTW - it's 'build' not 'built'.
[Fire Original Android Development] xenokc:
CM12.1 working great for me. Hope to see unlocked bootloader soon so that CM13 becomes a possibility.
[Fire Original Android Development] Deuces:
reboot fixed mine too
[Fire Original Android Development] :
You do know that my post is directly to [MENTION=5749760]ggow[/MENTION]? just in case you didn't see, but thanks for your opinion. And I was just giving my problems and see if [MENTION=5749760]ggow[/MENTION] could come with a fix for the next ( builts,builds, you still understanded me anyway. I'm not a fan of slimlp but a big fan of cm. but maybe stay on stock for now, thank you very much...... ;)

BTW-this ain't no spelling correcting site.
[Fire Original Android Development] DB126:
Public posts are open to community response. There are other tools for private communication.
[Fire Original Android Development] :
Its funny how you write things without analyzing, you told djflaco908 that when he posted about him also wanted to see optimization on someone else's post I seen that you told djflaco the exact thing I told you, that my post was directly to [MENTION=5749760]ggow[/MENTION]. So please stop making a fool out of yourself please. I seen half of your post trying to be Mr hot shot but guess that didn't work this time. M.Y.O.B next time
[Fire Original Android Development] sd_shadow:
If you want a private conversation, use Private Messaging

but Most devs are busy with their real life/jobs... and may not answer questions very quickly if at all.