yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] qtotter:
for those who tried to install cm12.1 over cm12.1 with bigger gapps installed by flashfire and got the errors below in the log and simply got your fire rebooted without any flashing, just install gapps mini first by flashfire and let it reboot. When it comes back to Android, install cm/supersu/gapps as you like. i have no idea what's wrong with gapps or flashfire, but this is the way you can update cm12.1 with bigger gapps.
[Fire Original Android Development] krawhitham:
The tablet see my Fire TV but fails to connect. I get a pop up on the Fire TV asking for permission, I select accept but it always fails to connect
[Fire Original Android Development] ggow:
- Will take a look into it before the next release

- Could you send me log?
[Fire Original Android Development] Signor Rossi:
I will test this a bit later with my fire tv too. What kind of logs do you need in case it's not working?

Gesendet von meinem A0001 mit Tapatalk
[Fire Original Android Development] asjimene:
Thanks for this ROM. I just got the tablet yesterday and I am amazed at how stable this ROM is so soon after release. (Didn't this tablet come out just a few moths ago?) Anyway, much thanks on the ROM, it is running perfectly so far!
[Fire Original Android Development] krawhitham:
sure, where is it at on the system
[Fire Original Android Development] ggow:
- A logcat that captures connection attempts, successes and failures
[Fire Original Android Development] ggow:
You'll have to capture a logcat with adb
[Fire Original Android Development] Signor Rossi:
I can't find my fire TV at all.

Still want me to send logs?

http://imgur.com/iQNdOlv

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] glate:
Is your Fire TV rooted? Updates blocked? Miracast (WiFi Display) is buggy and doesn't work in some (most in my experience) of the older Fire TV ROMs.
[Fire Original Android Development] Signor Rossi:
Ah, OK. My Fire TV is stock untempered

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] :
Thank you [MENTION=288149]qtotter[/MENTION] you a life saver. I gaved up after attempting to flash from cm,slimrom,stock rom and nothing. It was like flashing nothing but then i saw your post so i went to give it a shot and boom It installed normally with no problems.
[Fire Original Android Development] fmc000:
I don't use flashfire but I think that this information should be part of the faq

OH, wait, it's already there.
[Fire Original Android Development] der-mali:
The Fire tablet and your TV (Stick) must usw the same router (WiFi hotspot) and your router settings must allow that your devices see each other.

It works well with my Fire tablet and a Fire TV stick.

Maybe try an update of your TV device/stick.

See also my post #1265 above.
[Fire Original Android Development] Signor Rossi:
So, do I need root on my fire TV? And do I need to start any application on it?

Well, this TV is not in my network and I still see it

Spoiler content hidden.

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1

---------- Post added at 08:46 PM ---------- Previous post was at 08:32 PM ----------

Different question, does Tapatalk crash for everyone when you try to upload a picture?

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] Deuces:
works fine with chromecast.
[Fire Original Android Development] qtotter:
I wanted to find a smarter solution, but at the moment, this was the easiest way...
[Fire Original Android Development] :
Xposed

heyy atleast is something,something that works. ;)
[Fire Original Android Development] blueberry.sky:
Not all mention of lucky patcher is banned. Just mentioning using lp for piracy. I know that is it's primary use for most people but there is a minority that uses it for other things. But of course he had to mention "patch google play store" which doesn't have any purpose other than piracy. So yea, :eek:
[Fire Original Android Development] DB126:
Works great! Obviously some UI candy and power control modules have limitations due to CM skin/features. But Xposed itself and most modules are 100% compatible.
[Fire Original Android Development] :
Thanks a lot [MENTION=5488402]Davey126[/MENTION]. And also just a question more, installing xposed is it beneficial? I got like 3 modules but I see 1 works but don't know if others does.
[Fire Original Android Development] DB126:
You are fine IMO. Fixed OP and provided explanation. No one is on a witch hunt - just want to avoid discourse on potentially illegal/unethical tools and methods (operative word being 'potentially'). See XDA terms if interested.
[Fire Original Android Development] :
Thanks once again for the details and for head up. I appreciate it really. I won't happen again
[Fire Original Android Development] DB126:
CM's extended UI mitigates the need for many modules but it depends what you are looking for. On one device I have a dozen, another no framework/modules at all. Both users are quite happy. I see no need for Xposed for core functionality but modules can certainly bring nice 'enhancements' the value of which is determined by the user.

I noticed a slight increase in boot times (3-5 sec) with Xpoxed Framework installed but have not performed a detailed analysis to track down the culprit. Likely a module vs the framework itself but there are no smoking guns in my carefully vetted portfolio. Curiosity for another day ...

Edit: Xposed modules can interfere with the boot process and (worst case) require low level intervention to rectify, especially those that mess with core processes. The risk is small with mature modules; a quick search will usually surface a module's reputation on various device types.

There are some that believe Xposed is a security risk. Rooting itself it the real culprit. Xposed and supporting modules are simply a visible/ethical/supported suite of 'apps' that leverage the vulnerabilities exposed through rooting. If concerned you really need to be worried about what you don't see...
[Fire Original Android Development] :
That's what I wanted to hear, I thought installing XP will bring core functionality. Hmmm I was trying some modules like I mentioned but seeing it installed and active doesn't really do a dime. Yes I also notice the increase of boot time and when I first flashed it I thought I was in a bootloop but after 10-15 mins I was up and running again. But I maybe take XP out
[Fire Original Android Development] LenAsh:
Not quite... any mention is "two strikes and out"

6. Do not post or request warez.

If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
[Fire Original Android Development] glate:
I've got two CM devices: the Fire (Jan 4 build) and a Note 3 (hltetmo nightly Jan 5 build). I wanted to test WiFi Display so I went ahead and upgraded my Fire TV to 51.1.6.3_516012020.

The Note 3 and my Windows 10 machine can both find and cast to the Fire TV. The Fire tablet says "No nearby devices were found".

My Fire TV is *wired* in case that matters. They are all on the same network segment.

I've got no use for WiFi Display so ignore me if it works for others but I'm happy to provide any logs if it's helpful in any way.
[Fire Original Android Development] Signor Rossi:
Sorry I meant.... More discussions on this topic please ?

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] :
Edited: i get your reason and as a respect I don't think you need to keep going with this. I already edited my post a long time ago.
[Fire Original Android Development] LenAsh:
?? - I wasn't quoting you.... I was clarifying a statement made by the person i DID quote.

I saw that you had edited your post already, thanks.
[Fire Original Android Development] glate:
Doh, user error on my part. For those who are getting "No nearby devices were found." on their tablet go to Settings, Display & lights, Cast Screen. Then click the three dots (top right) and check the radio button "Enable wireless display".

It's not very intuitive but it doesn't search for devices unless that is checked. The display shows "No nearby devices were found" rather than "Wireless display not enabled". I should have read [MENTION=4620188]der-mali[/MENTION]'s post completely I suppose :(
[Fire Original Android Development] Signor Rossi:
I did this already, but it did not help

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] :
Oh my apologies then, yes I edited that's why I thought you was referring it to me lol
[Fire Original Android Development] fastcar22:
i am getting strange error cannot flash file because of incompitable data. please try reflash or factory reset when i use latest cyanogenmod rom and flashfire. please let me know what ia m doing wrong?

i have rooted the device and installed flashfire.
[Fire Original Android Development] :
Well there's a walk around this, I don't take any credit on this fix because someone already came with the solution. And its easy process.

First flash pico gapps and let the tablet reboot to normal then flash the ROM and SuperSU and then mini gapps.
[Fire Original Android Development] fastcar22:
now i have a another error i loaded slimrom which was successful and now tried to get to cyanogen from slim rom and got stuck at patching system image unconditionally message in flash fire. how long does it take its been 30 mins.
[Fire Original Android Development] :
Same happened to me at first. I think you stuck on a bootloop. The only way to get out is to return back to fireos and thats using adb to push the firmware that you currently have installed. Then root the tablet and flash ROM and SuperSU and gapps. About flashing pico gapps then rebooting then flashing ROM,su,gapps I thought you was on cm previous built. so you was on slim, mmmm try to see if you can get cm previous built dated 20151230 then if flashing succeed then do the steps I mentioned earlier, flashing pico gapps,reboot,flash ROM,SuperSU,gapps. I had the same problem but in my case I was already on cm previous built. I think the dev can pm you with previous built to flash first but other than that I can't help. But someone here might be more helpful than I
[Fire Original Android Development] fastcar22:
how can i get to recovery mode on 5.1.1 ?? i cannot see recovery mode when i hold power and volume up button it just says amazon and reboots again.
[Fire Original Android Development] :
That's strange, let say you have your tablet on portrait view so power off the tablet completly then press volume key down next to headphone jack, then press power button and wait you'll see Amazon logo continue holding both buttons untill you see stock recovery
[Fire Original Android Development] fastcar22:
yeah i tried that it just reboots without recovery, when i try the other button i can go to fastboot mode.
[Fire Original Android Development] :
Mmmm do you have any recovery installed? At least you can use fastboot, I think there's a way around this with fastboot but that's out of my knowledge. I never used fastboot but I know you can cmd with fastboot but I'm not sure. Try holding both buttons at the same time and keep holding until you see stock recovery. Don't hold 1 button and then the next, hold both at the same time both on point
[Fire Original Android Development] glate:
AFAIK recovery can't be installed (besides the Amazon stock) since the bootloader is locked.
[Fire Original Android Development] :
Is there anyway he can get back to stock using fastboot? He said that he can't get into stock recovery so I was assuming that something touched the stock recovery like flashing
[Fire Original Android Development] fastcar22:
I can get to fastboot using the volume up button and power button but cannot get in to recovery from there since its 5.1.1
[Fire Original Android Development] :
Don't worry someone here will have a solution on what to do with fastboot, if I knew exactly what to do with no doubt I'll help you through the process. ;)
[Fire Original Android Development] fastcar22:
Thanks djflaco908 hoping for the same I tried "fastboot install and zip file name" in the command window it errors out saying the zip file does not contain android-info.txt file so cannot install. Hope some android guru's can shed some light on how to install rom using fastboot
[Fire Original Android Development] der-mali:
Instructions how to enable WiFi Display ( Cast )

Instructions how to enable

WiFi Display

aka

Cast screen

Casting

See also my post #1265
[Fire Original Android Development] blueberry.sky:
I know you're a mod & I intend no disrespect but I have to disagree with interpreting the rules as, any & all mention of lp is banned. There is at least one legitimate thread concerning lp on xda. It's just that most people mentioning lp will be looking to use it for piracy. I'm sure the vast majority. I do avoid initiating any mention of lp tho.
[Fire Original Android Development] qtotter:
Someone also mentioned the same situation in my blog that he cannot get into recovery.

I also googled to find this article; http://mobile.tumblrvip.com/2016/01...-1-1-stuck-in-bootloop-with-no-recovery-help/

The common situation here is that they all tried to switch from SlimLP to cm 12.1 by FlashFire and got stuck in the middle of flashing before flashing SuperSU, and lost recovery. I can hardly understand how FlashFire can mess up stock recovery...
[Fire Original Android Development] sd_shadow:
it should not effect stock recovery, but something is definitely not working correctly

you link is just a copy of this thread http://xdaforums.com/showthread.php?p=64678702
[Fire Original Android Development] :
That same issue happened to me It was stuck on patching system... But I forced poweroff and turned on and I was in a bootloop so I went and rebooted to stock recovery and really this happened to me only with cm built but I never lost recovery doing what I did
[Fire Original Android Development] qtotter:
The issue here is some people cannot longer get into stock recovery...
[Fire Original Android Development] :
i think so to because i flashed slimlp to see whats going on so i flashed back to cm got stuck on patching system image.... so i hard force tablet to shutdown and i still can boot into recovery
[Fire Original Android Development] fastcar22:
Hi Djflaco908 were you on 5.0.1 amazon stock rom or 5.1.1? i was on 5.1.1 before i flashed slimop rom, and can you please tell us how were you able to get to recovery after you got stuck with cyanogen boot logo? was it just vul-up plus power until you see amazon logo and let power button go??
[Fire Original Android Development] :
I was on fireos 5.1.1 ever since i started flashing ROMs. This happend to me with yesterday testing 3 times. I was stuck upon flashing cm built. 2 times coming from slimlp and yesterday coming from rr ROM and while tempting to flash it got stuck on patching system image unconditional...... So I holded the power button intill the tablet shutoff then I turned it back on and I was in cm logo bootloop so i turned it off again, then I holded vol down not up and power button while off and amazon logo came out and I kept holding both buttons intill I seen amazon stock recovery. ( put your tablet on portrait and completely off, then press the volume down <---- not ----> and now hold the power button, now keep holding both button and you will see the tablet turn on and you'll see the amazon logo but keep holding both button till you see amazon stock recovery.
[Fire Original Android Development] fastcar22:
Hi djflaco908, to make sure if i am pointing the right buttons, the button next to the headphone jack is the vol-up button, and the button next to the power button is vol-down button, in my case when i hold vol-up(button next to headphone jack) with power button it gets stuck on amazon logo, if the hold vol-down(button next to the power button) with power button it goes in to fastboot mode. and how long did you have to hold both buttons until you go to recovery? 30 secs or 60 secs?

thanks in advance
[Fire Original Android Development] will_ssi:
Hey all,

My 2015 Fire 7" updated the stock rom to 5.1.1 so I used FlashFire and changed roms to the Jan 4th CM 12.1 release in this thread. I wiped all settings via FlashFire, including cache except for the external memory (SD card), and made sure the wipe command executed before the flash. When flashing the ROM, I select the mini gapps release linked in the first post of this thread, but it didn't update. I've since tried older 230 and 430 releases from APK mirror, the SlimLP gapps release for the Fire 7", and even some older 5.0 / CM12 mirrors of gapps on sd_shadow's google page.

So what gives! What am I doing wrong? I'm using FlashFire to install all the zip releases of gapps, and the built in CM 12.1 file manager to install .apks. The apks install, but instantly crash when I reboot ("stopped responding.."). After a failed install, I've uninstalled Google Settings by the normal hold-drag-to-trash method. For the FlashFire failures, the .zips just aren't taking and there's no log in the SD card where I'm trying to install it from. When I flashed from 5.1.1 to CM 12.1 and included gapps from here, I did get a text log in my SD card that just said my system architecture is incompatible.

Any help would be appreciate, I'm half-way there!
[Fire Original Android Development] :
Well I'm testing the volumes and the one next to the headphone jack brings my volume down and the one next to power button brings my volume up. I just hold it till I see recovery. Mmm try volume down <----- and power button with the tablet turned off. Now keep hold both button till you see amazon logo now let go of power button only and keep holding volume down next to headphone phone till recovery pops up
[Fire Original Android Development] qtotter:
Flashfire log is saved in the internal storage.

---------- Post added at 03:54 PM ---------- Previous post was at 02:57 PM ----------

Something must be preventing it from getting into recovery. Have you tried wiping data and dalvik cache partitions from bootloader?
[Fire Original Android Development] matthew5384:
[MENTION=5749760]ggow[/MENTION] had any time to look into the OpenGL errors?
[Fire Original Android Development] :
You mean recovery mode? For my understanding the bootloader is locked on 5.1.1
[Fire Original Android Development] DB126:
You can not clear cache and dalvik (still used by ART) on a device that can not boot a custom recovery. There are ways to pull this off from a running OS or via adb but it's not easy.

Stock recovery clears the cache and data partitions but leaves system alone. Not sure about the others.

Currently there is no method to unlock the bootloader on 2015 ford's regardless of FireOS version. The 5.0.1 bootloader contained a vulnerability that permitted a custom recovery (typically twrp) to be booted but not permanently installed. That would require an unlocked bootloader or some other exploit like signature forging. A clever method was devised that allowed upgrading FireOS to 5.1.1 while retaining the 5.0.1 bootloader. That method is not available on devices that shipped with FireOS 5.1.1 or arrived at that version via OTA update from Amazon. They can not boot twrp nor access tools that permit manual wiping of selected partitions.
[Fire Original Android Development] :
Hmmm strange

---------- Post added at 06:22 PM ---------- Previous post was at 05:43 PM ----------

Not quite right, because flash fire you can wipe cache,dalvik,ART,internal,3rd party apps,system data,cache portion and no need of adb. Now for people who can't boot into stock recovery well idk. That's 1 reason i don't do dirty flashing because some data can become corrupted and bam have a tablet acting funny
[Fire Original Android Development] :
Just notice that after installing cm it creates a WiFi hotspot, is there anyway to stop the WiFi hotspot? The tablet is under my name Luis and when I went to WiFi I seen Luis.b and connected it and found out that Luis.b in on my WiFi. Last time to test i did factory defaults and Luis.b was gone and now again I connected to WiFi Luis.b is showing again. So there's no doubt that the ROM is creating WiFi hotspot
[Fire Original Android Development] DB126:
Good catch on FlashFire. Wasn't thinking about that tool which has certainly evolved and is a great/essential asset to those with post 5.0.x ford bootloaders. Like most I prefer twrp (fortunate enough to have that option) as it allows more precise control over flashing, not to mention backup/restore options that have saved my bacon on more than one occasion!
[Fire Original Android Development] :
Just started to use setcpu and found hotplug in it, does anybody know is this demand smooth? I find it little quicker
[Fire Original Android Development] qtotter:
no, i meant bootloader.

fastboot erase [partition] or fastboot format [partition]

edit:

it looks like erase and format are not supported on fire, either...
[Fire Original Android Development] DB126:
See: http://androidmodguide.blogspot.com/p/blog-page.html

(I like hotplug on this device; interactive works better on others)

Also take a peek at Kernel Adiutor. Same idea as SetCPU. Both are great.
[Fire Original Android Development] 11wallace11:
Amazing!

As an owner of a OPO I feel so much at home with this ROM.

After installing this ROM I finally started to love this tablet.

One small bug report:

Settings > Buttons > Reorient Volume Buttons indication is wrong (shows on when it's off and vice versa)

Keep up the great work!
[Fire Original Android Development] :
Yes because bootloader is locked on 5.1.1, well that's my understanding
[Fire Original Android Development] Signor Rossi:
Anyone tried Kodi with IPTV?

It's kinda working, just buffering every few seconds like hell.

It's what I've expected, but I just want to check if you got better results?

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] DB126:
Yes, of course. Can't execute privileged low level commands with a locked bootloader.
[Fire Original Android Development] :
Speaking of the bootloader, if the bootloader was unlock we can use a custom kernel overclocked? If there was one
[Fire Original Android Development] DB126:
Err, sure. But you won't get much out of an overclock. Cores are idle or throttled much of the time presumably waiting on slower components. This is budget tab; cranking up max cpu by 15-20% will hardly be noticeable. Go further and you'll likely see stability issues.

Don't get your hopes up on a BL unlock.
[Fire Original Android Development] :
Mmm that sucks really, na I rather stay with a locked bootloader and not a unlock one then
[Fire Original Android Development] sd_shadow:
there is no unlocking the bootloader
[Fire Original Android Development] :
Lol I was only saying in other words if there was ever aa zip to flash to unlock bootloader that I'll never go for it in other words. It was more of a joke since overclocked kernel won't bring stability to the budget tablet

---------- Post added at 06:49 PM ---------- Previous post was at 06:43 PM ----------

Hey [MENTION=4267571]sd_shadow[/MENTION], will cm13 ever come to fire 5th gen tablets? I see order fire has cm13 night
[Fire Original Android Development] DB126:
FYI - an unlocked bootloader brings a number of significant benefits unrated to overclocking.
[Fire Original Android Development] sd_shadow:
perhaps, but stock kernel isn't very compatible with cm13
[Fire Original Android Development] kingrat:
Is there a preferred way to upgrade from an old version to a newer version? Can someone tell me. thanks. Love this, works great!
[Fire Original Android Development] :
So in other words you saying if a unlock bootloader was to ever happen it will be beneficial besides the overclocked kernel?