Related
So I updated to FroYo manually thanks to the methods posted here. I've nearly reinstalled all my apps with the exclusion of one; Square. I cannot find it in the market and thought maybe the dev pulled it, but it shows up in 2.1 and web-based market browsers, just not in 2.2. Anyone else experiencing this? Can I just force the apk onto the phone somehow?
icanhazxda said:
So I updated to FroYo manually thanks to the methods posted here. I've nearly reinstalled all my apps with the exclusion of one; Square. I cannot find it in the market and thought maybe the dev pulled it, but it shows up in 2.1 and web-based market browsers, just not in 2.2. Anyone else experiencing this? Can I just force the apk onto the phone somehow?
Click to expand...
Click to collapse
Same here.. seems like the copy protected apps are having problems.
This is not root or something else regarded - everyone has these issues.
Regards
Great to hear I'm not alone, but being an early adopter can sometimes blow (in the BAD way) =\
Is this being discussed in another thread? I did a search prior to posting and came up empty
EDIT: Mods, thanks for moving this to the appropriate forum. I've seen mention of this issue appear in various threads, though no thread of it's own. Will wait for devs to catch up with 2.2
I reported the same problem on modaco last night... I'm sure google will enable de protected apps this week, just a slight oversight on their side.
i had same problem, just put them apk on your sd card and install it. if it is being a stubborn app like a certain few just copy/paste or move them to data/private-app and install from in there. should take care of it 4 u.
Same problem here (Tapatalk Pro and Extended Controls missing).
when you create an app you can set a max api level to support, or not.
applications that have that set won't show on newer devices.
exzeus, square, and a few others seem to have done it...
give them about a month or so and you should see them come around.
icanhazxda said:
Will wait for devs to catch up with 2.2
Click to expand...
Click to collapse
reporting in for the same problem!
My App ICE Donate wasn't found either.. I removed the copy protection until Froyo is officially listed - it can be found and downloaded again
I'm missing cachemate, I only see the free version and I've check the box for all sources for apps. astro will not install from my backups
-------------------------------------
Sent via the XDA Tapatalk App
found out if you sign in via wifi (as I've been doing - maybe even if you skip update at the beginning) things don't work right with the market...since my account is suspended I eventualyl signed in with my cousins sim and yea, it all works fine now...
AbsoluteDesignz said:
found out if you sign in via wifi (as I've been doing - maybe even if you skip update at the beginning) things don't work right with the market...since my account is suspended I eventualyl signed in with my cousins sim and yea, it all works fine now...
Click to expand...
Click to collapse
This cant be the reason. i did only do signin via edge!
Having the same issue here. Wife's N1 can't find WeatherBug Elite, or the Helix Launcher in the market. Even after reboot.
Same. Paul actually fixes it in his roms by changing the Rom fingerprint. Some of the unofficial nexus updates he integrated did the same thing to protected apps. Once fingerprint was changed, it seemed to have done the magic. I'm guessing that he will do the same next week for froyo.
Same here my paid app wont show up which means I may be losing sales so I'm pissed right now
Yeah, so no MLB app at the moment... which makes me unhappy.
Any word on an official response from Google yet on this issue?
theres a fix in this thread:
http://forum.xda-developers.com/showthread.php?p=6572697#post6572697
punk4bc said:
theres a fix in this thread:
http://forum.xda-developers.com/showthread.php?p=6572697#post6572697
Click to expand...
Click to collapse
Good looking out. Google needs to address this fast though for the non tech people (and potential app customers)
t0mmy said:
Good looking out. Google needs to address this fast though for the non tech people (and potential app customers)
Click to expand...
Click to collapse
the non tech people you speak of won't be running Froyo
Koush posted a new thread with the release of CM6 RC3 and this one will no longer be maintained.
Thanks to everyone for their testing and bug reports!
http://forum.xda-developers.com/showthread.php?t=755690
Thx, I hate having to read through all the other pages to get this. PLEASE edit with nightly builds.
Wireless tether works fine if u download it from the market.
Sent from my Incredible using XDA App
Quick question regarding the facebook sync. By reading your summary of the facebook, i wonder if i have a different issue. When i go to accounts and sync, when i click add then facebook. It just goes back to accounts page. Does not even let me enter facebook information. However i am able to use the facebook app.
Is this the bug your referring to, or am i experiencing something different?
killer2239 said:
Quick question regarding the facebook sync. By reading your summary of the facebook, i wonder if i have a different issue. When i go to accounts and sync, when i click add then facebook. It just goes back to accounts page. Does not even let me enter facebook information. However i am able to use the facebook app.
Is this the bug your referring to, or am i experiencing something different?
Click to expand...
Click to collapse
Yes. Does the same to me.
jermaine151 said:
Yes. Does the same to me.
Click to expand...
Click to collapse
Ok, thanks for clarifying. In your summary might want to put something regarding "Unable to add to accounts & sync" , just for others that might be curious.
Wireless tethering worked for me, i just installed the one provided in the 10minute root video again after CM6 was installed. Then tested it and it worked fine. I also have Hydra Rom for stock speed undervoted with wireless N. Noticed when i did tethering it only connected to my laptop in G mode, however i am able to connect to my router in strictly wireless N broadcast.
Had this problem last night which forced me to revert back to stock firmware.
I plugged in my phone to charge at 11 PM. Then at 12.30 ish AM, i heard my phone vibrating. I looked and it rebooted. So i let it be, then few minutes later I heard it again. Then I decided to revert back to Stock.
Thinking that it was maybe caused when charging the battery. That the batt got 100% then rebooted? Not quite sure.
I can test again if needed.
Good idea.
Thanks!
You are most welcome!
Thank You very much
what time is the nightly build and what time standard/zone?
i would love to try this but cant without bluetooth and am hoping it makes it into the next build. in my state they are cracking down on using your cell phone without a handsfree and giving big tickets to make up for budget shortfalls. so i need bluetooth. (i am too deaf for speakerphone, especially on the incredible, its not that loud)
i am excited, especially now i am 90% sure i am keeping the DINC now that the DX is officially going to be a ***** to root and no roms looks likely. and i dont know why blogs that pimp the phone keep saying "root is still inevitable" but i dont agree with that, if you cant get into the boot loader we would have never rooted the incredible and it only makes sense motorola has locked down the backflip root methods and made sure rooting will also be hard.
i just really want a bigger screen and a fast gpu, other than that, the DINC is the best.
cray1000, I edited the OP to answer your question on the build times.
You guys are all VERY welcome! I'm glad I can help make any of this easier. I can't develop (yet ) So this is my contribution for the many things I get from XDA, Koush and the other developers!
jermaine151 said:
cray1000, I edited the OP to answer your question on the build times.
You guys are all VERY welcome! I'm glad I can help make any of this easier. I can't develop (yet ) So this is my contribution for the many things I get from XDA, Koush and the other developers!
Click to expand...
Click to collapse
thanks man! keep up the good work!
and nice, based on your answer on the first post, we have a new build as of a couple hours ago, anyone running it yet? anyone have a revised bug list? should we discuss that here or in the other thread?
It would appear that the incredible has been removed from the buildbot cycle as of the latest build. A version was built today (check the dates) but looking here: http://buildbot.teamdouche.net/tgrid it's no longer listed
I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.
killer2239 said:
I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.
Click to expand...
Click to collapse
if you clear download cache and redownload it should be newer, someone posted the repo and it clearly showed a date and time of today even though the file name still said 7-8 or 7-9 on it the time and date were 7-10 unless it was mirrored then or osmething.
killer2239 said:
I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.
Click to expand...
Click to collapse
The filename doesn't change. Just clear the download cache in ROM manager and then choose download ROM, reinstall as usual. I guarantee its a different file. Updating OP with what my current build version shows.
Sometimes download of apps in market just stalls.
Some apps fail to install. (android-vnc)
Sometimes screen doesn't register touches until rotated.
jermaine151 said:
The filename doesn't change. Just clear the download cache in ROM manager and then choose download ROM, reinstall as usual. I guarantee its a different file. Updating OP with what my current build version shows.
Click to expand...
Click to collapse
Deleted the CM6 zip file from the sd card, then redownloaded the nightly build. Installed and noticed the rom version now has 7/11 as the date instead of the zip files number. So thats good. I see you crossed out the green light while charging bug. Thats only difference i have noticed thats been fixed.
I really hope they are concentrating on Facebook, Camera, GPS bug the most. Thats the biggest deal breaker for most i know.
Hi ya, i think i had 5.3.2.0 and rooted it via rootjunky's tool (kingroot then supersu) and flashed back to 5.3.1. blocked OTA updates and went for the custom Nexus ROM, kept coming up with google errors so dumped that and tried CM12.1 and still got various other errors so read on one of rootjunkys feeds that someone just gave up and kept 5.3.1. and just removed the "crap" as he called it so i have come to the conclusion i'm going to do that as well.
So as i stand right now i am at 5.3.1. rooted blocked OTA updates and kingroot has gone and supersu is in, playstore is due to go on via the 5thGenSuperTool and change the stock launcher to Nova, that is as far as i can go on my own, been hunting around on here for threads that help remove the unwanted Amazon which to be honest is all of them i think but i'd like to keep Calender/Calc/clock/camera app but even some of these need you to register the tablet before i can go any further, so as it stands right now what is best for me should i register the tablet or not, if yes should it be in real name or moody name?
Also i see mention of lock screen and adverts, sorry for the next question the lock screen is that the screen you come to first where you have to swipe upwards to see icons? And why have i not seen any adverts yet, is it because i have not registered the tablet yet?
Also can you suggest any other threads for me to look at regarding getting rid of the rubbish or bloatware just stuff i don't need, i have come across the following but just wondering if i have missed anything you can think will help me in my case.
https://forum.xda-developers.com/amazon-fire/general/removing-lock-screen-ads-root-t3218946
https://forum.xda-developers.com/amazon-fire/general/adb-shell-pm-hide-bloat-amazon-t3221466
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544
https://forum.xda-developers.com/amazon-fire/general/safe-to-remove-5-0-1-bloatware-2015-t3239582
Now i'll be the first to admit i have not read all of these threads yet, that is my plan next but i just wanted to see if i'm missing anything special that you think i should know before i go any further and also unsure what registering the tablet will do.
All1
Allonewordinuk said:
Hi ya, i think i had 5.3.2.0 and rooted it via rootjunky's tool (kingroot then supersu) and flashed back to 5.3.1. blocked OTA updates and went for the custom Nexus ROM, kept coming up with google errors so dumped that and tried CM12.1 and still got various other errors so read on one of rootjunkys feeds that someone just gave up and kept 5.3.1. and just removed the "crap" as he called it so i have come to the conclusion i'm going to do that as well.
So as i stand right now i am at 5.3.1. rooted blocked OTA updates and kingroot has gone and supersu is in, playstore is due to go on via the 5thGenSuperTool and change the stock launcher to Nova, that is as far as i can go on my own, been hunting around on here for threads that help remove the unwanted Amazon which to be honest is all of them i think but i'd like to keep Calender/Calc/clock/camera app but even some of these need you to register the tablet before i can go any further, so as it stands right now what is best for me should i register the tablet or not, if yes should it be in real name or moody name?
Also i see mention of lock screen and adverts, sorry for the next question the lock screen is that the screen you come to first where you have to swipe upwards to see icons? And why have i not seen any adverts yet, is it because i have not registered the tablet yet?
Also can you suggest any other threads for me to look at regarding getting rid of the rubbish or bloatware just stuff i don't need, i have come across the following but just wondering if i have missed anything you can think will help me in my case.
https://forum.xda-developers.com/amazon-fire/general/removing-lock-screen-ads-root-t3218946
https://forum.xda-developers.com/amazon-fire/general/adb-shell-pm-hide-bloat-amazon-t3221466
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544
https://forum.xda-developers.com/amazon-fire/general/safe-to-remove-5-0-1-bloatware-2015-t3239582
Now i'll be the first to admit i have not read all of these threads yet, that is my plan next but i just wanted to see if i'm missing anything special that you think i should know before i go any further and also unsure what registering the tablet will do.
All1
Click to expand...
Click to collapse
Hum - not aware of any persistent errors on CM 12.1. Stable, responsive ROM.
Davey126 said:
Hum - not aware of any persistent errors on CM 12.1. Stable, responsive ROM.
Click to expand...
Click to collapse
Yea i did get a couple but forgot to take not of what they were, i'll give CM 12.1 another go tonight and post back just for your info on what errors i got .
All1
Allonewordinuk said:
Yea i did get a couple but forgot to take not of what they were, i'll give CM 12.1 another go tonight and post back just for your info on what errors i got .
Click to expand...
Click to collapse
No ROM is perfect - custom or stock. Installation errors/omissions are a leading contributor to less than satisfactory outcomes. Post your experiences w/supporting detail; someone will try to help.
Davey126 said:
No ROM is perfect - custom or stock. Installation errors/omissions are a leading contributor to less than satisfactory outcomes. Post your experiences w/supporting detail; someone will try to help.
Click to expand...
Click to collapse
I'm having no issues with the ROM itself SuperSu has been a nightmare to update, i tried TWRP but for the life of me every thread i try to use (here and elsewhere) it fails to works and just lease a blank screen, if i remember last time my problems came with gapps and wondering what version of gapps i should use i have seen pico spoke about but can't even get that far, had the damm thing since black friday and to be honest i'm getting fed up with it
All1
Supersu has been updated and for the life of me i have no idea why but i don't care it's done, now to look at gapps
Well just to close this down, i have it working now my major problem was trying to install gapps v6 on it but once i had worked out my error she is fine, i just want to say thanks to everyone who has helped me get it sorted once and for all.
All1
Hey everyone,
So I've been trying to "modernize" my phone, since I'm under the impression that I can get another 2-3 years out of it. So far I have:
-Running 7.1.1 stock rooted w/Franco kernel
-Hacked to include Pixel launcher (works great)
-Hacked to include Assistant (works great)
-Hacked to run Daydream (works great(ish)) -These tutorials are all available online and are pretty simple if you kinda know what you're doing
I bought a Daydream headset and have been playing with the apps. Some seem to work fine, and some won't run, some won't install. This seems like pretty fresh territory, so I haven't found much help online.
I know our phone supposedly doesn't meet the intended hardware specs (thermal characteristics, and GPU speed?), but it sure seems capable enough to me.
-Home screen and remote - works no problem.
-Playstore - works no problem.
-Netflix VR - works no problem.
-Arts & Culture - works no problem.
-Asteroids - This is pretty awesome. It's a demo of an animated episode (not the old game). It has 3D sound, which I wasn't expecting since the Netflix VR app didn't have it.
-Youtube VR - won't install (sideload). A little research, and it sounds like this app won't run on our phone's architecture. As far as I know, I can't force it to run. I'm very interested in getting this to work though.
-NextVR - Launches to blank screen.
-Hello Mars - works no problem. Lacking content it seems.
-JauntVR - works no problem.
-Littlestar - opens to non-side-by-side screen.
-InceptionVR - opens to non-side-by-side screen.
-Etc.. haven't tried very many yet.
For some of these, I wonder... I have my phone "posing" as a Pixel XL. I wonder if it would make a difference if I changed it to Pixel regular instead.
Anyhow, there must be others out there who are interested in exploring Daydream on our Nexus 6. Please share your experiences/expertise or point to relevant threads I may have missed!
Unfortunately I am in the same situation as you are, but I am just as interested in getting it resolved. The Daydream UI and the apps that are working actually work very well. What I found is the apps that are opening single screen are doing so because of our device info. I can go into the build.prop and edit the ro.product.device to marlin instead of shamu the app will open in a side by side screen. The only problem is that my phone reboots after running for a few minutes (even if I am not in daydream). I emailed the app developer of "AFFECTED:The Manor" and he said they will adjust the app requirements in their next update, but we can't expect everyone to be so helpful. We need to come up with a way to edit the build.prop info without causing rebooting. Keep me posted and I will do the same ...
Very cool, glad I'm not alone here.
I did notice that Netflix seemed to have picked out that my device was a Shamu, but luckily at least that app doesn't care.
FYI it looks like a bunch more apps just got added to the in-Daydream app-store. Going to try a few of those, and also trying to get google photos working.
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
zelendel said:
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
Click to expand...
Click to collapse
Yes good point. I personally am prepared for the worst, but yeah, disclaimer to others...
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
needleyepoke said:
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
Click to expand...
Click to collapse
Get what to work?
stev067 said:
Get what to work?
Click to expand...
Click to collapse
The daydream app... Isn't that what this forum is about?
needleyepoke said:
The daydream app... Isn't that what this forum is about?
Click to expand...
Click to collapse
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
stev067 said:
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
Click to expand...
Click to collapse
I'll go back and check my steps.. Thanks
stev067 said:
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Click to expand...
Click to collapse
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
adbFreedom said:
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
Click to expand...
Click to collapse
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
stev067 said:
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
Click to expand...
Click to collapse
Yea, I had tried all combinations one at a time and all at once and my device would always reboot. I found during the trial and error that only the ro.product.device was what the app was reading, but could not stop the rebooting.
Cine Shot (Partial Motion Still Photos) working on LG V30 - APP link & Instructions.
Hey all, been a while since I've had any new discoveries because I have been busy with a move across the country, but I think this one was worth waiting for :good:
This post is a tough one to categorize, as its an "app" and its a "mod" but I also needed to include a little guide to help you all get it working. So I went with the Apps and Mods section, but if an Admin thinks this should go in the Guides section, I am totally cool with that.
Pre Install Notes:
This has been tested on my Rooted & Frankensteined LG V30 ThinQ LS-L998 on Sprint running US99827a software Security Patch Jan 1.19.
I do not know if this will work on non rooted devices simply because I haven't been able to test it on one. I do believe that this will work the same on a non-root V30 but I'll wait for confirmation from one of you... SOOOO if you have a non rooted device and you try this out, please let us know if its working.
Thank Yous:
A big thanks to @trouble. for requesting the G8 stock system apps in the G8 section & thanks to @iknow786 for originally providing the files which I used to make the link to the cineshot app below. If I did not happen across that thread we wouldn't have this new trick, so thank you both. Also a big thanks to all of the awesome folks that have kept the V30 development alive and kicking this long into the devices lifecycle. Very cool to see so many talented people still doing things for this community every single day. I cant begin to list everyone, but if you are active in here, you know who the folks are that have been grinding away at this all this time.
Ok so lets get you CineShooting!
Step 1) Go to the following link...
https://docs.google.com/uc?export=download&id=1Pxy8B1k19Q8ALiHc1FeYUHb3c8y4DnJI
Steo 1a) Download, and install the CineShot apk.
(Im hosting this on one of my drives, so if anyone has issues with the download, now or months from now, PM me and I'll fix it. If its a while from now and you just write "dead link" in this thread I prob won't see it, so that's why I am recommending a PM. )
(Since I have not yet figured out how to integrate this new app into our camera app, you will need to launch the CineShot main process using one of the programs I will mention in step 2. I am including some screenshots for those new to this. Hopefully this post will be updated in the future with how to integrate the cineshot capabilities into the regular camera section, but for now this is what we have)
Step 2) Once you have installed the CineShot apk to your device you will need a shortcut maker program to access it.
Personally I am partial to Shortcut Master, https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite&hl=en but other apps like "QuicksShortcutMaker" https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut&hl=en_US (tested and works) should word as well. So if you don't already have one, download one of those two or your own favorite.
Step 2a) Open your shortcut program and find CineShot by either scrolling to it or searching "Cine" or "CineShot". No matter which program you used you should see at least one option under the CineShot app ending with the words ".MainActivity ". Go ahead and favorite or create shortcut for this process, as you'll want to have a quick way to get back to CineShot mode. Now go ahead and click that option and your device should launch into cineshot mode.
Cine Shot Mode - How-To:
Pretty basic stuff here. Point and shoot at whatever you want (objects should be moving in your frame otherwise your just taking a normal picture). It will record 3 seconds. After it stabilizes your "video" it will then show you options to draw with your finger on the moving parts of the images that you still want to move. Do this, and then save. You now have a cineshot image with partial movement of the image.
That's it. Pretty easy stuff. If you followed the very simple steps you should be able to record using either your front or back camera, and cineshot should be fully working, or at least as fully as it can on our devices. Enjoy.
I don't have any fun stuff nearby to post a good example of a cool Cine Shot Pic, so if you guys and gals take any, please share so people can see what the fuss is about.
And as always, feel free to share the love with a click on that "Thanks" button if this post helped you out
*** Reserved for future post - updates ***
Side Note: From that same cache of G8 apks, I was able to get the My Avatar app partially working using the same steps as above but with that specific APK obviously. Unfortunately, while it will take my picture, it will not spit out an avatar, so some sort of framework or back end stuff is not enabled. Anyone that has access to the newer devices with this, if you can find the additional necessary files, we could prob get this working too.
Anyone interested in checking out the G8 stock apps in the original thread I mentioned above can find that thread here: https://forum.xda-developers.com/lg-g8/themes/lg-g8-preinstalled-apps-t3904050
Other apps that I got to install from the g8 are these: Humanavatar (My Avatar) LGContentsettings (Wallpaper and Theme. Not sure what this updates though) and an update to the Tasks app.
Be cautious installing things you don't know anything about. As always, its your phone, so beware, and there are no guarantees yada yada yada.
It doesn't integrate with the camera because only camera apps built for pie onwards have that functionality. Once enabled in camera config files it crashes the camera app immediately.
TotallyAnxious said:
It doesn't integrate with the camera because only camera apps built for pie onwards have that functionality. Once enabled in camera config files it crashes the camera app immediately.
Click to expand...
Click to collapse
Any idea why it crashes it? I mean other than it wasnt meant to work. Since the actual mode is functional I wonder if anything is actually missing in the Oreos framework/camera that needs to be there.
JonnyTrulove said:
Any idea why it crashes it? I mean other than it wasnt meant to work. Since the actual mode is functional I wonder if anything is actually missing in the Oreos framework/camera that needs to be there.
Click to expand...
Click to collapse
The app doesn't have the shortcut built in. Only camera apps built for pie or newer have it. It's not framework. It's just the camera app.
TotallyAnxious said:
The app doesn't have the shortcut built in. Only camera apps built for pie or newer have it. It's not framework. It's just the camera app.
Click to expand...
Click to collapse
Gotcha. That makes sense.
I'm glad you commented, as I was going to message you to ask your opinion on the My Avatar creation feature I mentioned after the original post. I can get it to snap a pic of my face, and it recognize I'm a person and takes the pic, but when it goes to process and spit out an Avatar it fails.
Since you're a good bit more advanced than I am, maybe you had an idea about what's keeping it from working.
JonnyTrulove said:
Gotcha. That makes sense.
I'm glad you commented, as I was going to message you to ask your opinion on the My Avatar creation feature I mentioned after the original post. I can get it to snap a pic of my face, and it recognize I'm a person and takes the pic, but when it goes to process and spit out an Avatar it fails.
Since you're a good bit more advanced than I am, maybe you had an idea about what's keeping it from working.
Click to expand...
Click to collapse
It'll likely be working on Pie. I've made a list things I'm not going to attempt till we get pie.
How did u install humanavatar? Is it good? Like ios
Works on V20D non rooted...
Appreciate it
trouble. said:
How did u install humanavatar? Is it good? Like ios
Click to expand...
Click to collapse
It installs normally but won't actually produce an Avatar. It trys to process the pic and then it fails.
JonnyTrulove said:
It installs normally but won't actually produce an Avatar. It trys to process the pic and then it fails.
Click to expand...
Click to collapse
Yep Same here
This is cool! Thanks!
Sent from my LG-US998 using Tapatalk
iIf you use Nova Launcher you can make a shortcut natively by making a new widget and choosing "activities".
Sent from my LG-LS998 using XDA Labs
APK file
There is a chance we can use modular downloadable camera modes using the same technique
Food mode, 360 panorama, square mode, ar, avatar, etc
We need to get those APK from LG g7/v40 oreo