i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
minjiet said:
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
jalize said:
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
Click to expand...
Click to collapse
Ya, i'm rooted, now the n10 cant boot at all....what can i do?
anyone can show me step by step guide?
Or flash the Factory image with a bit editing. This should do: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
I got that as well on my N10. Stock, stock recovery rooted. Booting into recovery didn't help. The next morning it was the same thing, but after a while it shut itself off and when I was ready to flash a stock img, had the USB cable plugged into the laptop, I look at the N10 and it's booting just fine, then starts applying the update.
Not helpful I know, but just wanted to let you know it fixed itself, I did nothing. Good luck.
Same problem on stock rooted. Impossible to boot and to switch off the device. I've wait the nexus shut down by himself and after the update have been automaticaly installed on the boot. I'm always rooted. Strange.
Use http://www.afterdawn.com/software/s...l_devices/nexus_root_toolkit.cfm#all_versions app is the best to fix and very easy
Sent from my Nexus 10 using XDA Premium 4 mobile app
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
A fixed all my problems, i am on stock with the same problem on jelly bean 4.3, now rooted and again with a custom recovery.
Sent from my Nexus 10 using XDA Premium 4 mobile app
thanks for the help...my n10 back to normal automatically after i plug in charger...weird
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
DEinspanjer said:
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
Click to expand...
Click to collapse
When you cleared cache you lost the update package I believe, so it didn't update, when I received my OTA I had TWRP installed and it went through nicely. Maybe you should try it and then installing Stock Recovery again.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
I have a Nexus 10. I just took and installed the OTA that arriced 08/27/2013. I am not rooted or unlocked. It is only a wifi (not a carrier specific).
I have been sick since i took the first Ota several weeks ago. I was constantly having to reboot because it would drop the connection. Firefox was useless. And above all, I was unable to get Grassland Live wallpaper and Wind Turbine 3D to work.
It all works now!
Sent from my Nexus 10 using xda app-developers app
I just read in another thread that the issue as described is caused by apply the OTA when rooted. Just unroot then apply the OTA update and reboot. Assuming you are using SuperSU., it has an unroot option in the settings panel.
Good luck.
Related
My nexus 7 is rooted. Is that why it can't accept the 4.1.2 update? What should I do? It keeps reminding me to install the update every 15 minutes. When I try to, it just crashes.
Sent from my Nexus 7 using xda app-developers app
You want to eat from two tables ... ? It's your choice, original or rooted ...
Sent from my Nexus 7 using xda app-developers app
I'm trying to update it while keeping root. I downloaded ota root keeper. But I keep getting the "dead Android with red exclamation mark" screen every time I try to install the OTA update. I even tried its option to temporarily un-root before performing the update, but no luck. Anyone have any ideas?
Edit - Also I tried installing it manually. Used GooManager to install TWRP and tried installing 4.1.2 through it. Still fails every time. I'm disgusted.
Sent from my Nexus 7 using xda app-developers app
I had my Nexus 7 rooted w/ the "Google Nexus 7 Toolkit" and I was able to update to 4.1.2 w/o any problems.
Sent from my Nexus 7 using xda app-developers app
Having the same issue as well..Can't root.
Sent from my GT-I9100 using xda premium
---------- Post added at 02:41 PM ---------- Previous post was at 02:25 PM ----------
Well after trying again I finally successed doing so.
Sent from my GT-I9100 using xda premium
Backup--unroot--relock--update--unlock--reroot--recover? I'm brand new to this stuff (don't even have a N7 yet), but seems like this would work.
The stock update will only install with stock recovery being root has no effect. If you have changed system apps. Like to the 4.2 apps floating around could stop the update as well. Google does not care another root or unlocked. I would say do factory reset then update then root. Or download one of the stock cwm/twelve roms and be done with it.
Sent from my Nexus 7 using Tapatalk 2
Well it happened again. The 4.2.2 update is out and I can't update to it. Every time I try, I get the dead android error icon.
It sure gets old saying this, but...
The error message is recorded in the recovery log at
/cache/recovery/recovery.log
You will find that the problem has nothing to do with root per se - generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
In general, OTAs are not meant for customized ROMs - it is unreasonable for anyone to have an expectation that they will work correctly on a customized ROM.
But I didn't install a customized rom. I just rooted/unlocked it.
You can always download the update from Google's servers and flash it through fastboot. No hassle.
Bryon15 said:
But I didn't install a customized rom. I just rooted/unlocked it.
Click to expand...
Click to collapse
the proof is in the pudding...
...and the pudding is at /cache/recovery/recovery.log
bftb0 said:
generally the root user (or apps that were granted root privilege) have altered or deleted something in /system needed for the OTA to correctly complete.
Click to expand...
Click to collapse
Note that the recovery.log file gets overwritten every time you boot the recovery, so the thing you are trying to retrieve (let's say with the booted OS) will be from the immediately prior use of the recovery. So, attempt the OTA (let it fail), then boot into the OS and capture that file (using something which is root-privileged).
I just got my new Nexus 7, and the first thing I tried to do was update to 4.2. It arrived with 4.1.2. When I pressed update, it booted into recovery, and started the loading android animation, however at about half way a red exclamation point went on the screen. This stayed on until I just rebooted the device, and it was on 4.1.2. After this, I checked for the update, and it says "Your device is up to date." I cleared the services, and it downloaded the update, and the same thing happened!
I don't know much about manually installing from Google's factory image, and I honestly don't trust myself trying to manually update it...I would rather just use the OTA.
Why does this happen? Are there any ways to fix this?
How are you doing this, using adb sideload with the ota zip or ?
- Sent from my US Cellular SGS3
---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------
There's plenty of ota zip files that are the official ota which will allow you to upgrade.
Are you 100% stock or ?
- Sent from my US Cellular SGS3
yanksrock1000 said:
I just got my new Nexus 7, and the first thing I tried to do was update to 4.2. It arrived with 4.1.2. When I pressed update, it booted into recovery, and started the loading android animation, however at about half way a red exclamation point went on the screen. This stayed on until I just rebooted the device, and it was on 4.1.2. After this, I checked for the update, and it says "Your device is up to date." I cleared the services, and it downloaded the update, and the same thing happened!
I don't know much about manually installing from Google's factory image, and I honestly don't trust myself trying to manually update it...I would rather just use the OTA.
Why does this happen? Are there any ways to fix this?
Click to expand...
Click to collapse
Is the device rooted and have you modified any system files? This generally happens when the patch update system attempts to patch a file for the update but it's been modified or missing.
Cheers,
Kermee
Haven't modified a thing, its completely stock.
Sent from my Nexus 7 using xda app-developers app
Try doing a factory reset
Sent from my SGH-T959V using xda app-developers app
I'm running into the same exact situation, except I have a 16GB. Whenever I attempt to update to 4.2 I get the robot lying on its back with a red exclamation point in its belly.
Hey guys,
Regardless of my low post count, I'm not a noob when it comes to rooting\unlocking\flashing. With that being said, I've run into a few problems with my Nexus 4. I was making a nandroid backup of my most recent CM 10.1 nightly and decided to flash back to stock rooted in order to fix my bluetooth issues. When attempting to restore, I received an error stating that my MD5 sum didn't match. This happened to all but one of my backups and it would old restore part of my data before failing on the "working" backup. It would boot just fine, but it was basically a factory image and none of my downloaded applications restored execpt the icons. I realized that this image was pretty unstable so I took it one step further..... I decided to restore to factory stock by flashing the factory images from google (I snagged a copy before google pulled them). I ran the flash-all.bat and it restored everything with no issues.....but now it gets stuck on the nexus "X" during boot. I left it for about an hour and it's still on the "X". At this point, I decided to relock the bootloader and call google.
I realized that something is probably corrupt so I called Google and got an RMA but I won't get a new phone until LG makes more Nexus 4's (Nexi?, lol).
Does anyone have any ideas what could have happened? ANy ideas on how to fix this? I'd much rather fix this damn thing instead of going thru the RMA process.
Boot into stock recovery, clear cache and factory reset. You'll be up and running.
Sent from my Nexus 7 using xda premium
Maybe I'm more of a newb than I realize, lol.
How do I do that via stock rocovery? I just have the red triangle. I know how to do that in Team Win and CWM, but not in stock.
Boot into the bootloader by holding volume down and power.
Use the volume key to toggle to recovery and press power to select.
When you see the exclamation. Press volume up and power to open the recovery menu.
Then clear cache and factory reset.
Sent from my Nexus 7 using xda premium
El Daddy said:
Boot into the bootloader by holding volume down and power.
Use the volume key to toggle to recovery and press power to select.
When you see the exclamation. Press volume up and power to open the recovery menu.
Then clear cache and factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I went ahead and unlocked the bootloader again and flashed CWM touch in the meantime. I cleared cache and reset. Same result. It's just hanging on boot.
No you need to do this in the stock recovery.
Sent from my Nexus 7 using xda premium
El Daddy said:
No you need to do this in the stock recovery.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If I knew who you were......i'd kiss ya. Thanks man. It's fixed.
Now, just out of curiousity, why does that only work in stock recovery instead of a custom recovery?
Not entirely sure. The stock recovery wipe clears everything including data/media/
There also seems to be an issue with the bootloader not properly wiping the device. Hopefully they can fix the bug in a future update.
No kiss needed. Just a thanks and a virtual high five will do.
Sent from my Nexus 7 using xda premium
El Daddy said:
Not entirely sure. The stock recovery wipe clears everything including data/media/
There also seems to be an issue with the bootloader not properly wiping the device. Hopefully they can fix the bug in a future update.
No kiss needed. Just a thanks and a virtual high five will do.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I see what you mean about not wiping everything.....after all the wiping and flashing, it still had my same custom wallpaper from my CM 10.1 ROM when it booted. Weird.
Thanks again.
That's not because of something not getting wiped.
Its because your wallpaper syncs to Google. It's auto downloaded and applied when signing in for the first time.
Sent from my Nexus 7 using xda premium
Got OTA after clearing framwork services, decided to factory reset from settings/backup reset.
After it shut down it proceeded to boot, gets past the google logo and about 20 seconds into the "X" then the screen brightens briefly then it shuts down, was totally stock and locked.
Totally stumped as to why this has happened, and help/ideas would be greatly appreaciated.
Sent from my GT-P5110 using xda app-developers app
AW: Stock Nexus 7 wont boot after 4.2.2 update & factory reset
Put it on the charger for some time, at least half an hour, then try to start again. Looks to me as if you battery is too low.
Sent from my Nexus 7 using xda app-developers app
1 - unlock the bootloader
2 - flash stock 4.2.1 image from fastboot
3 - flash the ota zip
if doing so it doesn't work, you'll need someone more experienced than me to help you
Battery was at 70%+
Recovery showed no command
Left it on charge for about half hour, tried booting and it still didn't work then when I next picked it up it was showing the language selection screen. So go figure, its back up and running.
Sent from my Nexus 7 using xda app-developers app
alferret said:
Battery was at 70%+
Recovery showed no command
Left it on charge for about half hour, tried booting and it still didn't work then when I next picked it up it was showing the language selection screen. So go figure, its back up and running.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
same has happened to me could not get past the "x" so i factory reset still cant get past "x" put it on charge and will try again soon
alferret said:
Got OTA after clearing framwork services, decided to factory reset from settings/backup reset.
After it shut down it proceeded to boot, gets past the google logo and about 20 seconds into the "X" then the screen brightens briefly then it shuts down, was totally stock and locked.
Totally stumped as to why this has happened, and help/ideas would be greatly appreaciated.
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Why would you do a factory reset after flashing the OTA? Anyway, if all else fails, return to stock 4.2.1 and update through OTA again, or better yet sideload the update.
Leonhan said:
Why would you do a factory reset after flashing the OTA? Anyway, if all else fails, return to stock 4.2.1 and update through OTA again, or better yet sideload the update.
Click to expand...
Click to collapse
cant get mine pass the "x" all i done was updated ota then i factory reset it and its just stuck on "x" not to sure what to do im a newbie at flashing etc its in waranty so i may just talk to google/asus.
brianzion said:
cant get mine pass the "x" all i done was updated ota then i factory reset it and its just stuck on "x" not to sure what to do im a newbie at flashing etc its in waranty so i may just talk to google/asus.
Click to expand...
Click to collapse
Try flashing stock rom again, then OTA via the system updates in the settings menu.
I am running CM 10.2 by Skrilax - http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907 (Might be fine with the DHacker version also, but this is what I used.
Pretty much everything seems to work including GPS. I do not have Bluetooth anything so I can't speak to that. Some (maybe most) people seem to have difficulty getting it installed, but it can be done. There are a few tricks to it. Here's what worked for me:
I highly recommend using TWRP 2.6.0 as that's what I use and I know it works. Not sure whether other recoveries will function the same or not.
What you need:
1. The most recent version of CM 10.2 from the link above.
2. Gapps Core 4.3 - http://goo.im/devs/BaNkS/GApps 4.3
3. Root for 4.3 - http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip
1. Erase everything except the external sdcard. Do it three times. (Don't ask, just do it.)
2. Also Format Data - what the heck, do that 3 times too.
3. Install the CM 10.2 ROM, wipe dalvik and cache again and reboot into the system. DO NOT install anything else at this time for best results.
4. Let the OS boot all the way to the desktop.
5. Unlock the developer options by going into Settings\About Phone and tapping 8 times on Build number. (Only needs done one time, updates do not hide it again.)
6. In Developer options, change Root Access to "Apps and ADB". (Go ahead and set up whatever else you want in Settings.Do not install any apps or updates at this time.)
7. Reboot into Recovery. Install Gapps Core 4.3
8. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)
9. Once the phone boots all the way, reboot into Recovery again and install Root using Supersu 1.43.
10. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)
11. Once System has booted, you can update SuperSu in the Google Play Store. The first time you open it, it will want to update the binary. It's very important that you choose the option to do it from Recovery. Your phone will reboot into Recovery, update the binary and then boot back into System.
12. Once all this is done, so are you. Restore your apps, allow Google Play to do any updates, and customize the layout to your tastes.
Note: Once you get a successfully installed 10.2 setup, you can dirty flash the nightlies. Always clear dalvik and cache. And always backup your apps before flashing anything if you want to make your life easier.
ENJOY!!!
Going to give it a go with CWM I'll let you know how it goes.
Well I got the rom to work but I could not get it to boot after loading gapps. I tried wiping data but no joy!
Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!
I am not able to successfully root though. SuperSU complains:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"
I have tried to reflash the SuperSU zip posted here multiple times to no avail...
Thoughts?
EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Flashed TWRP and I was able to get it up and running having the same issue with root going to try the file above and I'll update again.
edit
*** the supersu 1.51 file worked for me as well. ***
---------- Post added at 04:43 PM ---------- Previous post was at 03:47 PM ----------
I'm still having issues. I got the root to work but everytime I reboot the device I have wipe data or it hangs on the boot logo.
---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------
Restored back to carbon rom 1.8. I may try again after a few more dailies are out. As this is my primary device I can not have the issues I saw. Admittedly it may be something that I did wrong and not the rom.
Sent from my XT907 using xda premium
Got this up and running last night and no issues so far for me. I'm wondering though if any custom kernels work with 10.2? I was curious about the vanquishpuppiesn12 kernel.
kensdavid said:
Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!
I am not able to successfully root though. SuperSU complains:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"
I have tried to reflash the SuperSU zip posted here multiple times to no avail...
Thoughts?
EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Click to expand...
Click to collapse
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters!
Sent from my XT907 using Tapatalk 4
Thanks for sharing , make a mark
netizenmt said:
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters!
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
can you confirm if rear mic is working when taking videos? this has been the only hangup for me on the 4.2.2 ROMs...
I doubt it, since that functionality is probably kernel related, but still just curious...
thanks!
Ok I noticed that I had somehow installed the wrong TWRP I installed 2.6.0 today and I have so far had good luck phone is up and running and seems to be stable. At first I had some issues with a few apps throwing errors during the mass install when I sync'ed with Google but a manual download after and they installed just fine. Also the new camera app called focal has some issues for me it opened and took pics but images in gallery are blank. However the stock camera app seems to working fine at least for stills I have not tried video yet.
I've got this all working too, including root. But I've been noticing about a second delay when pressing power to unlock the phone. Sometimes it delays so long that I press power again. So when the phone does wake up, the screen goes off again from my double press of impatience. I'm running the 0907 nighlty
Sent from my XT907 using XDA Premium 4 mobile app
FWIW, never needed to wipe data multiple times and I flashed everything at once. That said, still a good procedure to follow
Also, @georgeascott, that's a known bug. It tends to SOD on occasion... Not much to do to fix except maybe overclocking
Sent from my XT907 using Tapatalk 4
Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
Sent from my XT907 using xda app-developers app
zombolt said:
Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...
Can always hope someone will Dev for it though
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...
Can always hope someone will Dev for it though
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I have no clue how to do those things. I got really spoiled on the dinc. So many people spoon feeding contributions to a fabulous device. It sure is a shame it's impossible to unlock my boot loader
Sent from my XT907 using xda app-developers app
everything I've run into *works*
but it all doesn't work so smoothly
Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.
netizenmt,
Thx a lot for your help. I`m now on cm10.2, too.
But there seemed to be some bugs.
1.I cannot install any apps from Google Play Store, or it hangs on the MOTO logo after reboot.
2.I can take calls, but cannot reach the 3G network.
P.S.When I try to use QPST to configure the phone, the QPST tells Serious error encountered, write to phone aborted.
I've installed CM10.2 two weeks ago and everything is working great! The first time I flashed it I got stuck at the CM boot animation... After ten minutes spent watching it I forced it to reboot: stuck again. At this point I booted back to recovery, followed thoroughly netizenmt instructions (wipe three times, really!!!), installed CM10.2, Installed gapps, installed supersu v1.43 and so on (follow all the steps netizenmt told us!)... Everithing worked fine then. At this point I changed build.props to make the phone works in GSM mode.
fargles said:
everything I've run into *works*
but it all doesn't work so smoothly
Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.
Click to expand...
Click to collapse
If you go to settings/developer options and scroll down to HW overlays. Check the box to disable HW overlays. That should help with the tearing/chopping.
Also, maps FC all over the place as soon as you're using GPS.
Sent from my XT907 using xda app-developers app