yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] sajawal islam:
Hello every one...

i need help plzz ... i bought a cell phone samsung galaxy grand 2 sm g7106 and i have a problem with storage .. the phone shows two types of storage internal storage 8 gb and apps storage 2 gb.. so apps storage is almost full i can't download any new apps but the internal storage has 7.9 gb free.. so the question is how can i download apps or move apps to internal storage.. i'm so confused :confused: plz help ... my phone is made in korea by samsung... thanks
[General Questions and Answers] pantherdaddy27:
Go to your download

Settings and change the way it goes
[Fire Original Android Development] ggow:
IMPORTANT NOTICE​

:

As many of you know, the CM-12.1 branch will not be supported in the new LineageOS fork. And many of the new Google security patches are difficult and fiddly to back-port as they are now geared towards Marshmallow and Nougat. So as a result there will be no further updates to this rom.

Instead my focus will now be Fire Nexus ROM for this device.

Also looking at possible ways to get later android versions on the device. Will let you know if there is any progress later.

Thanks for all the support :good:

[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]

Current Progress

updated: 25 Jan 2016

Rules

- Please search the thread before asking questions

- Please try to stay on topic, I know it's not always possible

- Please report bugs here

- Report only one issue per bug report

- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...

- Saying something isn't working without proper explanation will not attract any attention.

Prerequisites for Installation

- If you have FireOS 5.0.1 then use Cyanogen Recovery or TWRP Image

- If you have FireOS >= 5.1.1 then use FlashFire 0.50

Fresh Installation from TWRP

- From your recovery perform a Factory Reset

- Flash the ROM File

- Flash Open Gapps - Use either micro, pico or nano

- Do NOT use stock gapps as there is not enough space on the /system partition

- Reboot and enjoy!

- Fresh Installation from FlashFire 0.50

- Click the Red + and choose 'Wipe'

- Ensure System data, 3rd party apps and Dalvik cache are CHECKED

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Cyanogenmod Zip

- Accept defaults

- Click the Red + button again and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Open Gapps Zip.

- Accept defaults

- Move "Wipe" to the Top of the order

- Press the big FLASH button.

Upgrading from FlashFire 0.50

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Cyanogenmod Zip

- Click the Red + button again and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Open Gapps Zip.

- Accept defaults

- Click the Red + again and choose 'Wipe'

- ONLY tick Dalvik and Cache.

- Press the big FLASH button.

Downloads

*** Please do NOT create any mirrors ***

- CM-12.1 for Amazon Fire 7" 2015 Tablet

- Open Gapps

Source Code

- Device Tree

- Kernel Source: Ford stock kernel, build number update-kindle-global-37.5.6.0_user_560177220

Thanks

- Cyanogenmod

- csolanol

- diegocr

- k4y0z

XDA:DevDB Information

CM-12.1 Amazon Fire 2015, ROM for the Amazon Fire

Contributors

ggow

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.10.x

Based On: Cyanogenmod

Version Information

Status: Stable

Created 2015-11-15

Last Updated 2017-02-03
[Fire Original Android Development] ggow:
Frequency Asked Questions

Question 1:

How do I adjust the keyboard sound level?

Answer:

- Go to settings -> Languages & input -> Android Keyboard -> Advanced -> Keypress sound volume

- Then adjust the slider to your preferred level

Question 2:

Why does the screen image seem stretched or distorted?

Answer:

- The actual pixels in the Fire's LCD are not perfectly square

- That causes some distortion. It is particularly noticeable with round icons & when the screen rotates.

- This issue also effects the stock amazon OS as well as all custom roms.

- It is not yet known if this will be fixable in software (my current thinking is probably not)

Question 3:

Why is my brightness slider not working?

Answer:

- Try installing Brightness Level and use it to change brightness. After doing this brightness slider should work fine and you can remove Brightness Level.

Question 4:

When installing Google Play Games and Google Calendar I get error -505?

Answer:

- Install older versions from apkmirror then update from Google Play Store.

Question 5:

How do I use CIFS?

Answer:

See the guide here
[Fire Original Android Development] bobbob1016:
Actual CM12.1 on the Fire 2015? So, a premium device for $50 with CM12.1? Awesome! Might have to pick one up now... I'd guess I don't have to fastboot each time I power on right? Just the first time to get CM/TWRP, then have CM/TWRP install+boot CM12.1, then I can get CM12.1 without fastboot?
[Fire Original Android Development] ggow:
- You will have to fastboot each time

- It's all in the OP including the reasons why this is the case at the moment.

- It's not ideal - but thought I would share what I have so far

- I am looking into solutions for this now.
[Fire Original Android Development] ggow:
- Links are now up
[Fire Original Android Development] bobbob1016:
Thanks for the hard work!
[Fire Original Android Development] blueberry.sky:
Once booted into CM12.1 we can make general system configuration changes, install apps, etc, correct? And will changes be be retained if we need to reboot (through fastboot)? If so, where will CM12.1 files be stored?
[Fire Original Android Development] ggow:
- Yes customise as much as you want - all will be retained.

- Your data and OS is stored on the /data and /system partition respectively

- The only thing you have to reload on a reboot through fastboot is the modified_boot.img which won't affect anything else.
[Fire Original Android Development] csolanol:
Awesome work [MENTION=5749760]ggow[/MENTION]!. [MENTION=4375260]diegocr[/MENTION] and me have been working on bring slimrom to this device. We are having some issues with WiFi and bluetooth. Would you mind to share your device and vendor for cyanogen?.

Thanks.
[Fire Original Android Development] ggow:
Hi csolanol,

- I am in the process of updating my bibucket with the most recent changes

- Having trouble with bluetooth too.

- Wifi is working fine - I got it working like this:

- put this in your device tree

- then add this to your boardconfig.mk:

[INDENT]WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_WLAN_DEVICE := mediatek
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mt66xx
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mt66xx
WIFI_DRIVER_FW_PATH_PARAM:="/dev/wmtWifi"
WIFI_DRIVER_FW_PATH_STA:=STA
WIFI_DRIVER_FW_PATH_AP:=AP
WIFI_DRIVER_FW_PATH_STA:=P2P[/INDENT]

- Then add this to your device.mk or equivalent

[INDENT]# wifi
PRODUCT_PACKAGES += \
lib_driver_cmd_mtk[/INDENT]

- Do not include the propriertary bin/wpa_supplicant when building otherwise you will get a build error

- Instead copy it into your ROM after building.

- Hope this helps for now.
[Fire Original Android Development] Awesomeslayerg:
Didnt whats his face say he used the original boot.img file to flash permenatnly asop without using fastboot every time?
[Fire Original Android Development] esmith818:
[IMG="Bye-bye Fire OS"]http://www.reactiongifs.us/wp-content/uploads/2013/07/its_working_star_wars.gif[/IMG]
[Fire Original Android Development] diegocr:
Thanks, I will wait bitbucket update :good:
[Fire Original Android Development] ggow:
- Yes, that was me who said that but Amazon have changed things since then.

- On the HDX at the time they were not enforcing an selinux policy

- Now that Amazon are enforcing it cannot work in the same way at least for the moment until a workaround is found.
[Fire Original Android Development] ggow:
- Did you guys find a way of been able boot Slim without having to fastboot a boot image each time?
[Fire Original Android Development] diegocr:
no, only fastboot
[Fire Original Android Development] ggow:
[MENTION=2511007]csolanol[/MENTION] and [MENTION=4375260]diegocr[/MENTION]

I have linked my Device Tree in the OP.
[Fire Original Android Development] diegocr:
Thanks a ton :good:
[Fire Original Android Development] ggow:
- I built my ROM without block based image generation

- This means you can extract the ROM and use the proprietary-files.txt with the extract-files.sh to re-generate the vendor tree
[Fire Original Android Development] qtotter:
This table is so great! Thanks for your extra work!!
[Fire Original Android Development] ggow:
- exFat requires kernel modification so we cannot use this at the moment.

- If the bootloader becomes unlocked then support for exFat and NTFS could easily be added.
[Fire Original Android Development] qtotter:
This 20151122 ROM seems snappier than the one released on 20151116!

What a great job, ggow! Fire is now totally a different machine!

Oh, 128gb SDCX card seems to be working now. Thanks for your update!!!
[Fire Original Android Development] MERLev:
I am experiencing strange random shutdowns. It mainly happens in games, but may happen while browsing too. Also, seems like happens much oftenly while on charging (first time i installed CM - I was not even able to finish initial setup,while charging it in parallel). Is there any way to log this thing to find reason for this? I've tried 20151122 and 20151116 roms with superSU and picoGAPPS flashed.

My friend also has CM on his fire, and also is expiriencing shutdowns, but not as often as me - several a day, as he said. For me - it may happen after several minutes of usage.

Also, i tried to use Kernel Auditor, and i got instant shutdown right after selecting interactive cpu proile.

I will try to get logcat today evening, hope there will be some clues
[Fire Original Android Development] ggow:
- Which apps/games are causing the random shutdown issue?

- I haven't noticed any random reboots whilst charging - verified from checking the uptime in settings

- We are limited to using the stock kernel which is why when selecting interactive cpu profile you get a crash.
[Fire Original Android Development] MERLev:
Monument Valley, Civilization Revolution 2, Google Chrome, Initial Setup after rom just installed.

Rom installed after factory reset and wipe of the /system and Internal Storage

Also, I had using it with Fire OS for nearly two weeks - and this never happened
[Fire Original Android Development] ggow:
Will take a look into it.
[Fire Original Android Development] sandman512:
Is there a way to turn off all sounds when pressing on any buttons(such as home button). FYI, I am using Swiftkey and have the sounds turned off when depressing the keyboard. Thanks!

Sandman

PS: Great Work.
[Fire Original Android Development] blueberry.sky:
Did you try these settings?
[Fire Original Android Development] sandman512:
LOL, I did check those prior to posting and I am still getting the sounds when pressing the Home button. Thanks.
[Fire Original Android Development] zach61797:
Settings-sounds-othersounds-touch sound toggle. Mines off and there is no home button sound
[Fire Original Android Development] ggow:
- I've been unable to replicate any of the issues you are having with random reboots

- I have run several games, multiple runs of Geekbench and Antutu and Chrome with no issue.

- The level of feedback overall is not enough to know how far spread or how many people may be experiencing the issue

- Any logs you can provide may help
[Fire Original Android Development] sandman512:
Thanks, much appreciated!:)
[Fire Original Android Development] theophile2:
Shouldn't it be possible, at least theoretically, to compile and insert new modules for the existing kernel to add functionality such as a filesystem support and CPU governors? Maybe the kernel implementation is different in Android, but I know that in Linux, you can build and insert new modules in place, without recompiling or replacing the kernel itself.
[Fire Original Android Development] MERLev:
Spent several hour today - with no results, lol. Haven't got even one shutdown - all is ok. Maybe it is because all this time i had 100% battery and usb connected. Will try to discharge and then check it again, as it seems like problem is someway connected with battery/charging. If I will be able to reproduce it and got logs - I'll make you know.
[Fire Original Android Development] jonboykayaks:
I have been running this firmware on my fire since the 11-16 build and have not had any stability issues with anything I have run. I have run several demanding games and apps and have had not one single lockup or random reboot.
[Fire Original Android Development] MERLev:
So, i finally got logcat ( spent more then a hour in civ 2 revolution) of that shutdown issue, but can't find anything strange except bluetooth errors

Logcat is in attachments
[Fire Original Android Development] Awesomeslayerg:
Did you try a clean install?
[Fire Original Android Development] MERLev:
All tests done on firmware after clean install - factory reset + /system and internal storage wipe. Latest version CM + SuperSU + pico gapps
[Fire Original Android Development] ktetreault14:
Does MHL work on this rom

HDMI Out
[Fire Original Android Development] wulfie66:
running the 'release' version of CM 12.1 on my galaxy s3 and there IS an unmount sd as well as format sd in storage settings
[Fire Original Android Development] DB126:
Hum. Plenty of posts from S3 users complaining the feature is missing. Might be parallel code branches. Not close enough to the CM project to knowledgeably comment further.

The unmount option does appear for OTG devices. So the code/UI is there - just not exposed for certain types of drives/interfaces.
[Fire Original Android Development] wulfie66:
well I guess the only 'safe' way to remove the sd from a fire is to power down, otherwise you'll corrupt it
[Fire Original Android Development] DB126:
Disagree if you are know SD card is not being written to. Depends what is on the device. I remove/replace SD card without hesitation as it only contains replaceable files that are read on demand. Haven't corrupted a card yet (although I certainly acknowledge it can happen).

The only thing I am challenging is the certainty of corruption on physical removal - not the possibility it could happen - and likely will happen if the card is being actively written to.
[Fire Original Android Development] blueberry.sky:
No SDcard unmount option is why I moved to SlimLP. Never had an issue unmounting in SlimLP or other roms.

Perhaps CM fears problems from users who aren't aware they have apps using the SD card? Still I wouldn't understand CM's problem, throw a toggle in settings with a big scary warning on it if you must, but don't completely rip out the unmount option.
[Fire Original Android Development] jrodat:
I have not corrupted a card either. If you know for sure no apps are using it, afaik the only other factor is OS write caching.. It's where write operations may remain in queue indefinitely until the OS decides to commit them. In Windows you can disable write caching on a drive, so that you can remove USB drives w/o warning. I do not know if CM/Android does write caching, or if it is/can be disabled.
[Fire Original Android Development] Dread This Day:
Is it actually possible to update to a newer build via Flashfire? When I try I get the error "Warning: It has been detected that you are trying to flash a block-level OTA, but your system/, /vendor, or /OEM partition has been modified. This will likely cause the flash to fail." And then yes, it fails. Just wondering if it IS possible and I am doing it incorrectly, or if I need to use a recovery via fastboot. Thank you.
[Fire Original Android Development] anselmo884:
Just ignore the warnings it'll work fine :good:
[Fire Original Android Development] Dread This Day:
HM, I have tried, and when the tablet boots and I look at the Cyanogenmod version, it's still the build I was trying to update. I must be doing something incorrectly.
[Fire Original Android Development] DB126:
- there's a link to FlashFire 0.27 somewhere - or grab a copy from ChainFire's G+ page

- be sure to the check the OP for recommended options and FlashFire task sequencing

- the warning you are seeing is not relevant to this device/rom and can be ignored

- not sure why the flash is failing; double check everything; read through the thread
[Fire Original Android Development] Dread This Day:
Frustrating and confusing. After installing .27 Flashfire, which is what I've been using the whole time, but did it to be positive, and following the thread directions for updating via Flashfire, I get the same results. Flashfire loads into the flashing screen, says it's flashing the ROM, then just reboots without flashing anything. Guess I'll just have to bite the bullet and hook it up with fastboot.
[Fire Original Android Development] jrodat:
I don't trust a dirty flash. I always wipe the /system partition + both caches before a system install or upgrade. Have never had a problem.
[Fire Original Android Development] Volkswagen04:
Fresh CM 12 install on three Amazon Fires

I just bought three Amazon fires for the kids. I rooted them and flashed CM 12. I just booted them up and they seem to have lost root access. I pushed chainfire's SU app via adb to each device thinking that was all that was missing, but nothing changed. Is this normal behavior? How do I regain root access without having to jump though hoops to make it work? I tried reading through the entirety the 200+ pages of this post to see if anyone else asked the same question but I could not find anything. Please forgive me if this is a repost. Thanks in advance.

---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------

I had this same issue. I tried it about five times on three different tablets and it failed every time. I followed these steps exactly and it worked:

- Click the Red + and choose 'Wipe'

- Ensure System data, 3rd party apps and Dalvik cache are CHECKED

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Cyanogenmod Zip

- Ensure Auto-mount and Mount /system read/write are UNCHECKED

- Click the Red + button again and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Open Gapps Zip.

- Ensure Auto-mount and Mount /system read/write are UNCHECKED

- Move "Wipe" to the Top of the order

- Press the big FLASH button.
[Fire Original Android Development] sd_shadow:
CM12's root access is off by default

settings>about tablet >tap on build number 7+ times, to enable Dev options>go back to Settings>Developer options>Root access>Apps and ADB

then reboot
[Fire Original Android Development] jrodat:
[double post]
[Fire Original Android Development] Volkswagen04:
That did it. Thank you sir!
[Fire Original Android Development] Dread This Day:
I tried this, the only difference is I lost all of my apps, etc. Flash still unsuccessful. Wonder if my download of the ROM is corrupted, but that is such a rare problem for me.
[Fire Original Android Development] DB126:
Rather strange. Musings:

- helpful pointers here (especially 1st post)

- always good to validate md5 if available; if not download target file a few times and compare md5 values; should be the same (imperfect method but better than nothing)

- keep it simple; minimize the amount of stuff being flashed in each run

- leave 'Mount /system read/write' checked (won't hurt)

- if still no love try checking 'Auto-mount' (read up on what it does if concerned)

- assume you are coming from FireOS? If so you may want to try a 'factory reset' from the stock recovery menu
[Fire Original Android Development] Dread This Day:
I redownloaded three times, all checked out, none flash. Also, I'm only trying to flash the ROM and GAPPS, can't get much simpler than that, I suppose I could just do the ROM, but I imagine that won't make a difference. I'll try leaving the mount option checked, and the auto-mount. I'm on the last build of this ROM, attempting to update to the 02/19 build.
[Fire Original Android Development] DB126:
- you don't need GAaps if simply updating rom builds

- make sure root is enabled and active (grasping at falling feathers)

- if you do opt to reflash GAaps keep it small (nano) and separate from rom flash

- if all else fails try flashing a different rom (Nexus or SlimLP) then retry CM

- recognize every FlashFire run entails some risk; plan each carefully and minimize attempts (I realize that sounds incredibly stupid given your current situation but would be remiss in not pointing out the risk; then again this is a $50 USD device...)
[Fire Original Android Development] Dread This Day:
Nods. Gapps only became involved after dirty flashing wasn't taking, I assumed wiping would help. But yes, I will definitely take your advice and try a different ROM, and minimize attempts. Thank you for your suggestions, greatly appreciated.
[Fire Original Android Development] Dread This Day:
Update, I wiped, flashed Slim ROM, wiped, and flashed the newest build here and GAPPS without incident. Strange.
[Fire Original Android Development] hobbit19:
You do build firmware for the HD8 / HD10?
[Fire Original Android Development] DB126:
Wrong forum; check here: http://xdaforums.com/hd8-hd10
[Fire Original Android Development] wulfie66:
probably a very dumb question, but I noticed in the screenshot that it says 'android 5.1.1', does that mean it'll update my 5.0.1 to 5.1.1 and I'll be stuck using flashfire in the future to flash updates?
[Fire Original Android Development] ggow:
In short, no you won't be upgraded to a later version of fireos
[Fire Original Android Development] wulfie66:
so it'll be android 5.1.1 but fireOS 5.0.1?
[Fire Original Android Development] DB126:
Yep - seen this before. The leading zero in the latest versions of FlashFire remind us this great tool remains a work in process.

---------- Post added at 08:46 AM ---------- Previous post was at 08:05 AM ----------

Amazon's Fire Operating System (FireOS) is irrelevant once replaced with CM or any other custom rom. Other components (bootloader/kernel/recovery) come along for the ride when FireOS is installed/updated using Amazon's native tools (OTA updates). As the bootloader remains locked those components are left intact when flashing an Operating System with a non-OEM tool like TWRP or FlashFire.

Specific to your question the version of Android depends on the ROM being flashed but must be in the 5.x (Lollipop) series due to kernel dependencies. The bootloader remains unchanged; in your case that appears to be version 5.0.1 and will never change unless you restore FireOS and allow it to self-update (not entirely accurate but sufficient for this discussion). The 5.1.1 designation you are seeing in the screen shots refers to the Android version.
[Fire Original Android Development] DigiAngel69:
After wiping and installing this and pico gapps, I am told it's not rooted? Is there a way I can test this? SuperSU fails to update binaries and FlashFire says it's not rooted :(
[Fire Original Android Development] DB126:
This has been covered soooooo many times:

- settings->build->about tablet: tap build number repeatedly until developer options enabled

- settings->developer options->root access

SuperSU can be layered on if desired.
[Fire Original Android Development] platypoid:
I think all you have to do is go to the developer settings and enable root . I did that and suddenly SuperSU appeared.