Related
So finally Android 4.3 has arrived and our Beloved Nexus 7 is Upgradable Now.....
here is the link to the download of factory Image:
https://developers.google.com/android/nexus/images#nakasijwr66v
Follow this Method and flash the New Android OS...
[GUIDE] Flashing a Factory Image with fastboot / return to stock Thanks @comminus for a great Guide...
Report Back with screenShots and new featuers as well as Bugs because new pudates bring New Bugs.....
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
hassam_tariq2003 said:
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
Click to expand...
Click to collapse
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
tbonezx11 said:
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
Click to expand...
Click to collapse
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
mhl12 said:
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
Click to expand...
Click to collapse
haven't tried it (I'm yet to receive the update) but someone referenced this link: https://plus.google.com/u/0/+Chainfire/posts/WqS2E9kkN1L
he is right.....You loose root but bootloader remains unlocked...
i have heard people say that you do not loose root if you use the OTA Method and your bootloader also remains unlocked....So its your choice its either Fastboot or OTA...
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Yeah OTA wont work for most people, seeing as they probably have a modified ROM. In any sense, chainfire has a root method that works. I can confirm it working, because I installed it using TWRP
khaytsus said:
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Click to expand...
Click to collapse
When 4.2.2 came out I had problems updating because my ROM was modified. But someone modified OTA not to check for changes in ROM and it worked.
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
I am running 4.3 unlocked but I did the one click method for root using nexus tool kit and for some reason it did not work, I have to try again tonight.
Want a single click ADB setup? Go to my thread I've made a Tool for that. No need to download the whole SDK it's just 2MB
http://forum.xda-developers.com/showthread.php?t=2374071
What to know how to easily pull ota link with ADB follow my thread.
http://forum.xda-developers.com/showthread.php?t=2270429
For official nexus 7 windows 7 - 8 driver download them from ASUS site. No trickery needed.
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
So, I played around a bit,
First of all, I did a "clean, unrooted and even locked bootloader install".
So I'm 1000% stock, just to avoid stuff like "maybe root caused it"..
(I locked it because I wanted to go 100% stock, just FYI, I know it's normally not necessary...)
The welcome screen was a bit weird... I got asked 2 times to tick or untick boxes for saving passwords and all that stuff.. (I think they mixed up the new and the old "first boot setup"?)
The Apps and widgets in the drawer were kinda confused, took 2 reboots for them to settle... (Icons disappeared and reappeared.. The widget tab in the drawer threw some widgets in and out, and the previews were mixed up, so dots and a weird sign was the result (as a preview of the widget)...
The initial setup was pretty laggy, but after setting stuff up, until now, yes I can say the performance of the nexus 7 is improved..
First I was like "OH HELL NO" but after the setup and the reboot everything was smooth...
Oh, and the back button was destroyed 1 time, blinked up but didn't go back... I pressed the home button and it worked then.
Edit: And sadly, no new wallpapers in stock... ):
Sent from my Nexus 7 using xda premium
I booted it up, restored my Google Play stuff (flashed a factory image, completely wiped everything from it, so it's clean, I think).
It lagged a lot, so I rebooted it and it still isn't 4.2.2 smooth. Maybe it's just me, I'll see.
Is it just me, or does it feel like the only thing that changed for us is the number in settings menu besides Google Apps?
OpenGL ES as it was already said, doesn't appear to be here for us, not to mention the fact that Miracast had never actually worked on N7 until recently when someone had it ported over.
Has anyone managed to find the link for the OTA yet?
SO I flashed the stock 4.3 kernel on a 4.2.2 rom and discovered that the stock android 4.3 kernel breaks wifi and gps on 4.2.2...
Eregoth said:
Has anyone managed to find the link for the OTA yet?
Click to expand...
Click to collapse
I have literally hours working on that.
Flashed the stock image using fastboot, took like 2 minutes to do, flashed the chainfire root patch and rebooted and restored apps, so far everything is pretty smooth no disappearing apps or icons or buttons, the kernel seems to be quicker, opening websites was quite a bit quicker, one thing I noticed while trying out different browsers was ads opening up new tabs automatically, that's something that's never happened before.
ffaiz.m said:
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
Click to expand...
Click to collapse
Tegra 3 does not support GLES3. Even Tegra 4 won't, because nvidia are still using their old gpu architecture.
What's the performance like? Better than 4.2 or 4.1?
Sent from my GT-I9300 using xda premium
Safestrap users, see ggow's thread instead.
Using draxie's tool (upHDX), I've created TWRP-friendly ZIPs of the stock firmware that leave the recovery and bootloader intact. Moreover, I've disabled OTA updates as well as lockscreen ads.
I'll try to keep this thread up-to-date should Amazon push any new versions. Feel free to make requests for any previous releases.
4.5.5 (user_455001320)
thor
apollo
Side note: if anyone's ever worked with the AROMA installer, shoot me a PM.
That‘s really great.
Maybe someday we will have the whole family of TWRP flashable HDX Fire OS. :smile:
---
BTW
any way to root it?
FotixChiang said:
That‘s really great.
Maybe someday we will have the whole family of TWRP flashable HDX Fire OS. :smile:
---
BTW
any way to root it?
Click to expand...
Click to collapse
I think you should be able to just flash a SuperSU ZIP over it.
Excellent - Thank you!!
EncryptedCurse said:
Safestrap users, see ggow's thread instead.
Using draxie's tool (upHDX), I've created TWRP-friendly ZIPs of the stock firmware that leave the recovery and bootloader intact. Moreover, I've disabled OTA updates.
I'll try to keep this thread up-to-date should Amazon push any new versions. Feel free to make requests for any previous releases.
4.5.5 (user_455001320)
thor
apollo
Side note: if anyone's ever worked with the AROMA installer, shoot me a PM.
Click to expand...
Click to collapse
I can't get this to work after wiping my system, dalvik cache, and cache partitions. It gets stuck at "Finishing startup..." or "Starting applications...".
Edit: Wiped /data and now it boots, but the setup screen force closes.
bmccoy11 said:
I can't get this to work after wiping my system, dalvik cache, and cache partitions. It gets stuck at "Finishing startup..." or "Starting applications...".
Edit: Wiped /data and now it boots, but the setup screen force closes.
Click to expand...
Click to collapse
Sorry, I didn't bother testing. Looks like I renamed one too many APKs that are required during setup.
I've uploaded the new versions (which should also disable lockscreen ads).
EncryptedCurse said:
Sorry, I didn't bother testing. Looks like I renamed one too many APKs that are required during setup.
I've uploaded the new versions (which should also disable lockscreen ads).
Click to expand...
Click to collapse
Looks like my Kindle is softbricked, for now, at least. For some reason, USB storage no longer works on my HDX and neither of my PCs recognize it in recovery or fastboot mode. Could you tell me the APK you renamed so I can rename it back in TWRP?
Anyone else having same issues?
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
I
And mega app wants to be used to download this .. Thanks for keeping this great tab relative..I'll hold a spell until the wrinkles are worked out
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
bmccoy11 said:
Looks like my Kindle is softbricked, for now, at least. For some reason, USB storage no longer works on my HDX and neither of my PCs recognize it in recovery or fastboot mode. Could you tell me the APK you renamed so I can rename it back in TWRP?
Click to expand...
Click to collapse
Try removing the .bak extension on /priv-app/DeviceSoftwareOTAContracts.apk and /app/otaverifier.apk.
Everything is working fine on my end, so I'm not sure what else to tell you.
EncryptedCurse said:
Try removing the .bak extension on /priv-app/DeviceSoftwareOTAContracts.apk and /app/otaverifier.apk.
Everything is working fine on my end, so I'm not sure what else to tell you.
Click to expand...
Click to collapse
I renamed those two applications back in TWRP, and it still isn't booting... :/
bmccoy11 said:
I renamed those two applications back in TWRP, and it still isn't booting... :/
Click to expand...
Click to collapse
You may want to refocus your efforts on getting device to communicate with a host in fastboot and then repair (reflash) twrp from there. Assuming you have an unlocked bootloader as that was a prerequisite for previous steps. I know it sounds stupid but try switching USB cables; amazing how often that works. Also do the driver dance on your preferred host, get rid of any hubs, only use USB2 ports, etc. Anything to get it communicating again.
You'll need to research how to flash twrp from fastboot. This is obviously dangerous and to my knowledge has not been attempted on a HDX. Theoretically possible and one of the many reasons for running with an unlocked bootloader. Good luck.
I have an unlocked bootloader (Apollo, have been running on 14.3.1.0 in a safestrap slot for the past two years, waiting for unlock, then flashed the bootloader update to 14.3.2.3 and TWRP 2.8.7.0), I did a basic wipe in TWRP, then flashed this ROM via TWRP, but after rebooting, then connecting to WiFi and entering my Amazon registration info, it asks for language selection then starts the normal UI temporarily then immediately goes back to asking for language selection, repeating over and over.
Davey
126 did it work for you. Love to try it
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
davekaz said:
Davey
126 did it work for you. Love to try it
Click to expand...
Click to collapse
Not yet - waiting for reported issue(s) to play out. Currently on Nexus v4 (v2 prior) and not missing out any Amazon functionality so would only flash this to confirm install procedures and basic functionality. Personal preference item; I understand some prefer FireOS UI and don't need access to Google Play/Services.
Davey126 said:
Not yet - waiting for reported issue(s) to play out. Currently on Nexus v4 (v2 prior) and not missing out any Amazon functionality so would only flash this to confirm install procedures and basic functionality. Personal preference item; I understand some prefer FireOS UI and don't need access to Google Play/Services.
Click to expand...
Click to collapse
Same I was just curious. I was on v4 and loving it but google services updated and started crashing continually so im on slim and besides Bluetooth issues its great. Thanks for reply
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
bmccoy11 said:
I renamed those two applications back in TWRP, and it still isn't booting... :/
Click to expand...
Click to collapse
adb works IN twrp, so as long as you have working adb and twrp, you can adb push a new zip to /sdcard to install...
Sent from my Kindle Fire HDX using Tapatalk
_Alex_ said:
fyi, adb works IN twrp, so as long as you have working adb and twrp, you can adb push a new zip to /sdcard to install...
Sent from my Kindle Fire HDX using Tapatalk
Click to expand...
Click to collapse
Of course, I've already tried ADB and fastboot. It won't show up in the device manager at all, I've tried different USB cables, different PCs, I even disassembled it to make sure the connections from the back plate to the mainboard were good. My mainboard must be bad.
bmccoy11 said:
Of course, I've already tried ADB and fastboot. It won't show up in the device manager at all, I've tried different USB cables, different PCs, I even disassembled it to make sure the connections from the back plate to the mainboard were good. My mainboard must be bad.
Click to expand...
Click to collapse
I just looked at the apollo image zip and noticed that the modem is still installed from the updater script... (hmm, your 4.5.2 for Thor also has the modem install too). I was just about to test drive this too, but I'm not up for modem backups tonight.
Has anyone ever gotten this to work?
Sent from my Kindle Fire HDX using Tapatalk
davekaz said:
Same I was just curious. I was on v4 and loving it but google services updated and started crashing continually so im on slim and besides Bluetooth issues its great. Thanks for reply
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As an aside I'm running v4 with the latest Google Services (7.8.99) and have not experienced any problems. FCs, etc are rare.
Davey126 said:
... how to flash twrp from fastboot. This is obviously dangerous and to my knowledge has not been attempted on a HDX. Theoretically possible and one of the many reasons for running with an unlocked bootloader. Good luck.
Click to expand...
Click to collapse
Just FYI @Davey126 flashing TWRP from fastboot is the easiest task that can be done with working fastboot (plus in case of HDX with unlocked bootloader, which is necessary). I did flash TWRP several times via fastboot just to confirm to me that I have unlocked bootloader...
Code:
fastboot flash recovery recovery_image_name.img
Obviously there is a lot of space for user error (faulty usb cable, corrupt download, drunk dude trying to do something he seen, hear, watched somewhere, etc.), and that is what is really dangerous here... irresponsible peoples trying to do something they do not understand (at least partially)...
Sorry, I often include screenshots to prove my assertions, but right now I am not in the mood to fight again with fastboot drivers for windows, which are probably live their own life thinking "G**O user, we are not going to flash ANYTHING today!"
So I turned on encryption today and it took about 5-10 to complete, yet it never asked for a password. I don't use key or gesture based passwords so it's kinda weird? Why would it encrypt without a password?
I've done some googling and it seems the default pass it "default_password". But that one doesn't work. I've done the same with my N7 2013 with the same story and my Optimus G test device does exactly the same.
It this a CM or TWRP bug since all my devices run both?
Sent from my XT1092
Sounds like a CM bug. In stock android when you encrypt it will ask you to choose a password or pin.
Sent from my XT1095 using Tapatalk
I see... Guess I'll just have to wipe the devices then and start over as I was planning on doing a clean install with october releases anyway.
Anyhow, I assume running stock is my only choice then? I'll start traveling around next month so having that extra layer of security is quite important in case anything happens.
PixelVixen said:
I see... Guess I'll just have to wipe the devices then and start over as I was planning on doing a clean install with october releases anyway.
Anyhow, I assume running stock is my only choice then? I'll start traveling around next month so having that extra layer of security is quite important in case anything happens.
Click to expand...
Click to collapse
I don't know if stock is your only choice. You would have to test various roms to see if it works. I just know stock works correctly because I just use a stock rom.
Sent from my XT1095 using Tapatalk
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
entermetallica said:
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
Click to expand...
Click to collapse
First of all congrats on the new phone. I'm on AT&T and updates came too slow for me. I chose to flash a system image to get upgraded to marshmallow and now we can download ota's directly from Google to keep up to date. Cutting out the need to wait for our updates to be made available from the carriers. Edit: to be clear you have to flash the ota's as well.
I believe others have removed sim card to try to get ota via wifi. I think. Anyway good luck.
Sent from my SM-T700 using Tapatalk
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Dopamin3 said:
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Click to expand...
Click to collapse
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
entermetallica said:
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
Click to expand...
Click to collapse
Assuming you're using Windows, if you look in device manager do you see anything either with a red x or yellow exclamation mark? If so you are missing the driver. This thread has the driver zip and briefly explains how to install it via device manager. Once you get the driver installed it should work fine.
And I can't remember if you need to or not to flash the stock images, but you might need to unlock your bootloader. Tap the build number a bunch of times and you will have access to developer options, and there you might need to check "Allow OEM unlocking" or something like that. Again I'm not 100% sure if that's necessary or not. I've ran my bootloader unlocked since day 1 and haven't looked back.
The bootloader does need to be unlocked to flash anything at all, except for a Google-signed OTA image.
Thanks for the help, ive done it. I had to boot into fastboot, and then install drivers from device manager
Sent from my Nexus 6 using XDA-Developers mobile app
Hi Guys,
So I recently got my hands on a kindle fire 5th gen (2015), running the latest OS 5.3.2.1.
I have read many things and many different opinions on what can and cannot be done, and ideally I am looking for a conclusive list i there is one available.
So I was searching and Root Junky has provided custom ROM's and a few other files, however, this is my understanding
CANNOT: root
CAN: downgrade to an older OS, which may allow root, but its likely it will brick it
CANNOT: unlock bootloader for custom ROM installation
CANNOT: install a custom flash zip file from the inbuilt android recovery interface
I dont know if they just happened to crash down and lockdown the fire recently, but pages such as this below, indicate it can (or at least could) be done.
https://www.thepolyglotdeveloper.com/2016/05/install-better-custom-rom-amazon-kindle-fire/
and this, indicates its probably too late since I connected it and downloaded 5.3.2.1.
http://android.stackexchange.com/qu...ot-and-install-cm-12-1-on-5th-gen-kindle-fire
So, is there a conclusive list, aside "using your tablet as out of the box" as to what you can and cannot do to modify the fire 5th gen?
I got mine right before bootloader lock running slim LP haven't updated since used flash fire on 5.1.1 to the best of my knowledge
Sent from my Robin using Tapatalk
FF51, so very lucky, I am really envious actually.
The fire, when not suffering pixel outages, and without a dire need for GPS, makes an excellent hardware base, and from my reading, installng a custom rom would really unlock the xperience of the tablet and give it a much more competitive edge.
Out of curiosity, did you jump straight into the slim build, or did you try others?
Also I have read you cannot install CM13+ due to the limitations of the bootloader, but can you install CM12 instead (I think thats based on lollipop isnt it?) and can you do that with the stock bootloader / recovery module?
jeebob said:
Also I have read you cannot install CM13+ due to the limitations of the bootloader, but can you install CM12 instead (I think thats based on lollipop isnt it?) and can you do that with the stock bootloader / recovery module?
Click to expand...
Click to collapse
- can not root (at present) or downgrade (ever) FireOS 5.3.2.1
- bootloader remains locked; no custom kernels or recoveries (eg: TWRP)
- rooted devices can only run Lollipop based ROMs due to kernel restrictions
- custom ROMs must be installed with FlashFire
- see forum index for further info: http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Davey126 said:
- can not root (at present) or downgrade (ever) FireOS 5.3.2.1
- bootloader remains locked; no custom kernels or recoveries (eg: TWRP)
- rooted devices can only run Lollipop based ROMs due to kernel restrictions
- custom ROMs must be installed with FlashFire
- see forum index for further info: http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks Davey, a concise list which is great, now I just have to hope we can get the bootloader and root sorted on 5.3.2.1!
bojkoio said:
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
Click to expand...
Click to collapse
It looks like the answer is not at this time, as from my reading, 5.3.2.1 cannot be rooted directly with current methods, only 5.3.1 onwards.
freaky2xd said:
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Click to expand...
Click to collapse
thats all I have managed to achieve so far, next I want to remove the adverts!
bojkoio said:
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
Click to expand...
Click to collapse
Nope - no custom ROMs without root.
---------- Post added at 12:50 PM ---------- Previous post was at 12:49 PM ----------
freaky2xd said:
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Click to expand...
Click to collapse
No - nor likely ever. Best hope is for a root solution.
Well Sh*t
I got all 3 of my daughters a kindle fire 7" 5th gen for Christmas. I ran thru the updates and was going to install the google framework and all that goes with it to be able to install works of ahhh painting app. However, I have hit a roadblock since it seems even tho I have enabled unknown sources and rebooted each device (all running 5.3.2.1) I can download apks but when I attempt to install them, it's like the install button just doesn't register touch response no matter what direction you rotate the device. I'm not new to this, I got kindles because of how easy it was to customize a previous one my 7 year old had, and besides, $30 each was a pretty good deal. So maybe it's a software glitch in the new update, maybe it's that I just don't care enough to dig into it but that's where it stands here.
Edit: A simple reboot after allowing unknown sources fixed the problem and I completed the installation of Google play store
luck_shawn said:
I got all 3 of my daughters a kindle fire 7" 5th gen for Christmas. I ran thru the updates and was going to install the google framework and all that goes with it to be able to install works of ahhh painting app. However, I have hit a roadblock since it seems even tho I have enabled unknown sources and rebooted each device (all running 5.3.2.1) I can download apks but when I attempt to install them, it's like the install button just doesn't register touch response no matter what direction you rotate the device. I'm not new to this, I got kindles because of how easy it was to customize a previous one my 7 year old had, and besides, $30 each was a pretty good deal. So maybe it's a software glitch in the new update, maybe it's that I just don't care enough to dig into it but that's where it stands here.
Click to expand...
Click to collapse
On mine I downloaded the four apks needed installed them (in proper order) using apk permission remover and it worked for me. There's a thread in the fourms I folllwed
I just used the kindle supertool to install the google framework and APK's. once click and leave it to its own devices - a tool by superjunky I think?
Anyway, as for the rotation, I havent noticed any particular problems with it, but I havent done a lot of work with testing it, I will try take a look a bit later!
i have the same problem. I managed to install Google Play but trying to side load the Popcorntime apk fails with the next and install button not registering touch input, cancel button works fine.
oilyrag said:
i have the same problem. I managed to install Google Play but trying to side load the Popcorntime apk fails with the next and install button not registering touch input, cancel button works fine.
Click to expand...
Click to collapse
Have you enabled FireOS setting that allows installs from unknown sources and then rebooted device?
Davey126 said:
Have you enabled FireOS setting that allows installs from unknown sources and then rebooted device?
Click to expand...
Click to collapse
Thought I had rebooted device, done it again, now works. Many thanks
Sent from my SM-N9005 using Tapatalk
I bought two 7" fires on the Black Friday sale to use as home automation panels in the house (with SmartThings). I installed the Play Store but found the SmartThings app was still not compatible . But really I was waiting for the new ActionTiles (web client) to come out. The one Fire upgraded to 5.3.2.1 and I haven't opened the other yet. The Play Store will no longer launch on the 5.3.2.1 tablet either. My original thought was to probably flash a new rom that is not as restrictive but doesn't look like that will happen now. Have a few additional questions for the "can" and "can't" list with 5.3.2.1 please:
1) Can the lock screen be disabled/removed?
2) Can the device be woken up by screen touch?
3) Does the non-root Play Store hack still work? (maybe I just need to redo something after the upgrade?)
4) Are there any browsers I can have auto load the ActionTiles dashboard (web page) and always keep it up and full screen?
Thanks a lot!
Coods said:
1) Can the lock screen be disabled/removed?
2) Can the device be woken up by screen touch?
3) Does the non-root Play Store hack still work? (maybe I just need to redo something after the upgrade?)
4) Are there any browsers I can have auto load the ActionTiles dashboard (web page) and always keep it up and full screen?
Thanks a lot!
Click to expand...
Click to collapse
1) not completely that I have found, unless you keep the screen alive 24/7.
2) power button only however root could allow this but 5.3.2.1 doesn't support (or should I say have a method for) root at this time.
3) yes it does, I have uploaded it to about 6 different kindle recently all running 5.3.2.1
4) again root would help, however you can use automateit free or pro from plastered. It's very powerful and you should be able to achieve a lot with it. If it doesn't support it though, tasker is another powerful tool which might be worth exploring
Sent from my D6603 using Tapatalk
jeebob said:
2) power button only however root could allow this but 5.3.2.1 doesn't support (or should I say have a method for) root at this time.
Click to expand...
Click to collapse
No hardware support for this capability regardless of root (re: touch to wake).
Davey126 said:
No hardware support for this capability regardless of root (re: touch to wake).
Click to expand...
Click to collapse
Thanks for confirming davey!
Sent from my D6603 using Tapatalk
Thanks for the info guys, appreciate it! This helps me understand the direction I want to take with these as alarm panels