(Q) PhotoSphere not in AOSP? - Nexus 4 Q&A, Help & Troubleshooting

Hi all and thanks for your time.
I was just curious if there was a way to enable photoshpere when compiling AOSP for Mako?
I have been searching but haven't been successful in finding an answer to this.
Again thanks for you help.

cteneyck said:
Hi all and thanks for your time.
I was just curious if there was a way to enable photoshpere when compiling AOSP for Mako?
I have been searching but haven't been successful in finding an answer to this.
Again thanks for you help.
Click to expand...
Click to collapse
its not part of the aosp afaik, its proprietary. you can overlay it with googles apk though.

Ok Thanks for the reply!

Can anyone elaborate on this a bit?
I'm building a vanilla AOSP for mako, installing the latest GAPPS from goo.im but I do not get the photosphere menu item. In /system/app I have GalleryGoogle.apk and GmsCore.apk which I understand are the proprietary apks from the GAPPS package.
Is there a setting somewhere that also needs overriding? (for example similar to the gesture keyboard which only works with the library file from GAPPS plus overriding the config_gesture_input_enabled_by_build_config setting in packages/inputmethods/LatinIME/java/res/values/gesture-input.xml)

i dont think goo apps include it. they are made for cm and they use the aosp variant. try extracting it fom stock android and you should be good, thats what we did and its working alright.

molesarecoming said:
i dont think goo apps include it. they are made for cm and they use the aosp variant. try extracting it fom stock android and you should be good, thats what we did and its working alright.
Click to expand...
Click to collapse
Did a bit more digging, and discovered the problem. The gapps package does install the required proprietary libraries & apks on the Nexus 4, but the photosphere functionality is only active if the the ro.product.model value in build.props is a supported product.
This value comes from the PRODUCT_MODEL in the build files (device/lge/mako/full_mako.mk). The value in the vanilla AOSP file is 'Full JellyBean on Mako'. Changing it to 'Nexus 4' activates the photosphere functionality.

nigelh2013 said:
Did a bit more digging, and discovered the problem. The gapps package does install the required proprietary libraries & apks on the Nexus 4, but the photosphere functionality is only active if the the ro.product.model value in build.props is a supported product.
This value comes from the PRODUCT_MODEL in the build files (device/lge/mako/full_mako.mk). The value in the vanilla AOSP file is 'Full JellyBean on Mako'. Changing it to 'Nexus 4' activates the photosphere functionality.
Click to expand...
Click to collapse
Thanks a million!

Related

Google Earth now claims it is incompatible with device

With my really smoothly working Cyanogenmod 7.2.0-RC1-encore I have been unable to install Google Earth. The app has been recently updated and does install on my CM 7.1.X devices but for some reason it refuses to make itself available for my CM 7.2.0-RC1 devices.
I've tried changing DPI, so that's not it, so what could be the problem?
Thanks much in advance.
aegrotatio said:
With my really smoothly working Cyanogenmod 7.2.0-RC1-encore I have been unable to install Google Earth. The app has been recently updated and does install on my CM 7.1.X devices but for some reason it refuses to make itself available for my CM 7.2.0-RC1 devices.
I've tried changing DPI, so that's not it, so what could be the problem?
Thanks much in advance.
Click to expand...
Click to collapse
It runs fine on RC1 so if you can get it on your device it will run. Copy it from one of your other devices.
Sent from my Nook Color running ICS and Tapatalk
aegrotatio said:
With my really smoothly working Cyanogenmod 7.2.0-RC1-encore I have been unable to install Google Earth. The app has been recently updated and does install on my CM 7.1.X devices but for some reason it refuses to make itself available for my CM 7.2.0-RC1 devices.
I've tried changing DPI, so that's not it, so what could be the problem?
Thanks much in advance.
Click to expand...
Click to collapse
Device information in build.prop (manufacturer, model and device)
Okay what do I change the values in build.prop to make it work again?

Help with themable mms and keyboard

Someone please help me out here. The ROM's I am running don't support the theme chooser theming the keyboard or mms. I have searched for hours and only found one zip that doesn't work. Any help would be appreciated.
Sent from my Nexus 4 using Tapatalk 2
Bump
Sent from my Nexus 4 using Xparent ICS Tapatalk 2
I suppose you are running PA?
The theme engine is made to interact with the AOSP apps, not the Google apps. Some developers use the apps from stock ROM's instead of the apps they build from source. Try picking the mms.apk and keyboard apk ( I think it's called LatinIME.apk ) from a CM nightly, put them in your /system/app folder, set the right permissions and reboot.
If this works it might be worthwhile to make a flashable zip of the apps you want to replace, there are quite a few of guides out there that teach you how to do this. But if you need help you can also just drop me a PM. Be sure to use the Edify language, and not the old Amend language which is still used in the old (3.x < I think) recoveries.
gangsterjoop said:
I suppose you are running PA?
The theme engine is made to interact with the AOSP apps, not the Google apps. Some developers use the apps from stock ROM's instead of the apps they build from source. Try picking the mms.apk and keyboard apk ( I think it's called LatinIME.apk ) from a CM nightly, put them in your /system/app folder, set the right permissions and reboot.
If this works it might be worthwhile to make a flashable zip of the apps you want to replace, there are quite a few of guides out there that teach you how to do this. But if you need help you can also just drop me a PM. Be sure to use the Edify language, and not the old Amend language which is still used in the old (3.x < I think) recoveries.
Click to expand...
Click to collapse
I appreciate the response man. I have started just flashing the goo gapps right after the pa gapps. Seems to get the job done.
Sent from a Paranoid N4

[MOD] Dialer (AOSP) to Google Dialer, works with odexed ROM/ART - NOW also themed!

*DELETED"
Always make a Nandroid before you try
Works perfect on 4.4 with an LG Optimus G
Thanks buddy! :good::highfive:
MiZrY said:
Works perfect on 4.4 with an LG Optimus G
Thanks buddy! :good::highfive:
Click to expand...
Click to collapse
It does not work on SlimKat Alpha 1.1 from my testing, including a full wipe afterwards as well as cache/dalvik only, tried twice as well.
If it works on houstonn's AOSP, it will probably work on his PA as well but I haven't tested that just yet.
I'm going to try to manually do it and report.
I have a Sprint HTC One running the latest CM11 build by "kushdeck" and just flashed the deodexed version. Following your steps provided all works flawlessly. Thanks so much for making this available to everyone.
~
Da Baron
Thanks you for the reports so far. Glad it works (for most of you).
Thyrus said:
Community,
As great as the custom ROMs are for the N5 on Kit Kat, the Google Dialer differs from the AOSP one included in many ROMs in certain aspects:
- uses the "old" 4.3 Phone Icon
- Misses the local search from your dialer app.
In order to help, I have put together 2 versions of the dialer, the teleservices (for phone) and the telephony provider.
Deodexed Version: Included all 3 apps deodexed (dialer, teleservices, telephony provider)
Odexed: Version; Contains APK and .odex files for the 3 apps
GAPPS uploaders are considering whether the Dialer is universal and may include it in their GAPPS in the neat future, for now, we need a seperate flashable zip.
Installation Change the dialer only: (ALWAYS make a backup before you test)
1. Depeding on your ROM, download the ODEX or DEODEX version. I highly recommend the odexed version, that is the one I use currently.
2. Install in recovery.
3. Clear cache/dalvik-cache
4. Reboot
NOTE: Depending on the ROM, you may see a f/c when booting from the com.android.phone apk. If that happens, you may need to WIPE your device and reboot. I have not understood yet why some roms have issues, and others do not. I just recently tested with a dirty wipe from CM11 to another AOSP rom, flashed the ROM, installed the Dialer-mod and it all works fine.
Downloads:
ODEXED Version
DEODEXED Version
Click to expand...
Click to collapse
Now I am flashing it on my Nexus S.
OK. Works well.
THX!
sadly no lucky on s4 cm11
Successfully running in latest slimkat release following the notes instructions in the OP. Just curious if I will be able to dirty flash with next slim release. Thanks for this as I like this feature.
Just noticed that BANKS gaaps now include this as well. If mine doesn't work maybe his will help you guys that can't get mine to work.
Thyrus said:
Just noticed that BANKS gaaps now include this as well. If mine doesn't work maybe his will help you guys that can't get mine to work.
Click to expand...
Click to collapse
That is just yours. And I changed the TeleService icon. I don't like an 4.3 icon in 4.4, even though it can't be seen in Google Home.
mushan3420 said:
That is just yours. And I changed the TeleService icon. I don't like an 4.3 icon in 4.4, even though it can't be seen in Google Home.
Click to expand...
Click to collapse
Not sure what you mean with "that's just yours???
Thyrus said:
Not sure what you mean with "that's just yours???
Click to expand...
Click to collapse
The TeleService.apk in BANKS gapps is the same as yours. If yours doesn't work, his doesn't, either.
Gotcha. The only thing he does differently is not deleting the aosp dialer.. Which means no FCS for people that had them before. Both banks and I are trying to figure you why it works on most Roms and some others require both dialers...
Sorry not working for Note 2, DND 3 custom os.
Sent from my GT-N7100 using xda app-developers app
Thyrus said:
Gotcha. The only thing he does differently is not deleting the aosp dialer.. Which means no FCS for people that had them before. Both banks and I are trying to figure you why it works on most Roms and some others require both dialers...
Click to expand...
Click to collapse
TeleService.apk (com.android.phone) (I will write TS for short.) is the most important apk.
When a call comes, TS in AOSP wakes up Dialer to show the answer button and interface, while TS in Nexus 5 wakes up Google Dialer.
So if the TS points to Google Dialer and works without FC, all the problems are resolved.
If we find that it doesn't work in some ROMs, that means the ROM requires a different TS.
mushan3420 said:
TeleService.apk (com.android.phone) (I will write TS for short.) is the most important apk.
When a call comes, TS in AOSP wakes up Dialer to show the answer button and interface, while TS in Nexus 5 wakes up Google Dialer.
So if the TS points to Google Dialer and works without FC, all the problems are resolved.
If we find that it doesn't work in some ROMs, that means the ROM requires a different TS.
Click to expand...
Click to collapse
true - however, given that my and his script replace the TS from AOSP with the Google TS -> it should, in theory, not matter which ROM. UNLESS there is a lib or something similar that calls a specific TS to work only....
Hello. I try your odexed version but doen't work. I'm on Beergang and in Europe. This feature is available only in US ?
techtium said:
Hello. I try your odexed version but doen't work. I'm on Beergang and in Europe. This feature is available only in US ?
Click to expand...
Click to collapse
works to me, beergang 0.3, flashed odexed version, and i'm from Serbia, thanx Thyrus :good:
works with beergang .03 thanks!
Sent from My Nexus⁴

P.A. Pie controls in other ROMS

Is the Paranoid Android Pie Controls (expanded desktop mode) open sourced and installable on other ROMS? I love PA's ROM mainly for that function but I also would like the stock LG apps such as the LG quick remote and wireless transfer. or does anyone know of a way to get them to work with PA. I tried extracting the APK files. no luck installing or moving to system/app. Also tried the ZIP file i found too with no luck.
Download LMT (somewhere on xda hahaha).
It's not COMPLETELY pie but it looks darn similar
Sent from my LG-D802 using xda app-developers app
r1nstang said:
Is the Paranoid Android Pie Controls (expanded desktop mode) open sourced and installable on other ROMS? I love PA's ROM mainly for that function but I also would like the stock LG apps such as the LG quick remote and wireless transfer. or does anyone know of a way to get them to work with PA. I tried extracting the APK files. no luck installing or moving to system/app. Also tried the ZIP file i found too with no luck.
Click to expand...
Click to collapse
The rom has to based on LG's framework in order for the LG specific apps to work. You will have to use LMT to get PIE like functionality on the stock rom.
nrage23 said:
The rom has to based on LG's framework in order for the LG specific apps to work. You will have to use LMT to get PIE like functionality on the stock rom.
Click to expand...
Click to collapse
crap I was afraid of that. I wasnt too impressed with LMT. im not sure what it is but it just doesnt seem as smooth as PA built in version

[ROM] AOSP 10 for sailfish

Hi everyone ,
prepare to be underwhelmed , i have got stock AOSP 10 buid QP1A.191105.003 ,
with vendor_gapps added , here is the link for that :
https://gitlab.com/MindTheGapps/vendor_gapps
that's it no modification , and it's a user build so it passes Basicintegrity ,
have fun .
DOWNLOAD :
https://mega.nz/#!LjBUlAIC!z1yQvDx2r8VHWvSvzcSng57Hxolztj5BA-b7TEbLNLc
AJ said:
Hi everyone ,
prepare to be underwhelmed , i have got stock AOSP 10 buid QP1A.191105.003 ,
with vendor_gapps added , here is the link for that :
https://gitlab.com/MindTheGapps/vendor_gapps
that's it no modification , and it's a user build so it passes Basicintegrity ,
have fun .
DOWNLOAD :
https://mega.nz/#!LjBUlAIC!z1yQvDx2r8VHWvSvzcSng57Hxolztj5BA-b7TEbLNLc
Click to expand...
Click to collapse
Error: incorrect zip format when installing through twrl
Dr.Lost said:
Error: incorrect zip format when installing through twrl
Click to expand...
Click to collapse
it is not a TWRP flashable zip , you have to extract the content of the zip & then flash the content trough fastboot ,
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img (if your main slot is a then flash with this command)
fastboot flash vendor vendor.img
with fastboot binary inside the unziped folder , or cd to the directory if you are on linux ,
hope this helps .
AJ said:
it is not a TWRP flashable zip , you have to extract the content of the zip & then flash the content trough fastboot ,
with fastboot binary inside the unziped folder , or cd to the directory if you are on linux ,
hope this helps .
Click to expand...
Click to collapse
Understood thank you
Just flashed but it didn't work. Phone said: " Your device has loaded a different operating system". Is this rom for Pixel (sailfish)? Thanks
hawksnake said:
Just flashed but it didn't work. Phone said: " Your device has loaded a different operating system". Is this rom for Pixel (sailfish)? Thanks
Click to expand...
Click to collapse
Follow the instructions, make sure you flash the stock factory image from google website
Thanks for sharing this. Exactly what I wanted, nice and lean
ROM?
How do you unlock the bootloader of sailfish updated to Android Q? There's a decent amount of people who're saying that the manufacturers shipped it with a locked bootloader in order to prevent the use of custom ROMS.
AJ said:
Hi everyone ,
prepare to be underwhelmed , i have got stock AOSP 10 buid QP1A.191105.003 ,
with vendor_gapps added , here is the link for that :
that's it no modification , and it's a user build so it passes Basicintegrity ,
have fun .
DOWNLOAD :[/B
Click to expand...
Click to collapse
Nightshadex543 said:
How do you unlock the bootloader of sailfish updated to Android Q? There's a decent amount of people who're saying that the manufacturers shipped it with a locked bootloader in order to prevent the use of custom ROMS.
AJ said:
Hi everyone ,
prepare to be underwhelmed , i have got stock AOSP 10 buid QP1A.191105.003 ,
with vendor_gapps added , here is the link for that :
that's it no modification , and it's a user build so it passes Basicintegrity ,
have fun .
DOWNLOAD :[/B
Click to expand...
Click to collapse
Try :
fastboot flashing unlock
Click to expand...
Click to collapse
Can i try with locked bootloader...?
Needed a change. Thank You for your work! I like VANILLA. (Really I do)
Edit1... Found the news link on Pixel launcher in any 10. It does work if you want it. Just followed instructions, it worked. OnePlus 6 Guides >Get Pixel Launcher with Overview Selection on Android 10< I know Vanilla and I added sprinkles <>
I understand correctly, this is a November patch that has not officially been released?
_Melkiy_ said:
I understand correctly, this is a November patch that has not officially been released?
Click to expand...
Click to collapse
It has been officially released to aosp
JS.zip said:
It has been officially released to aosp
Click to expand...
Click to collapse
No Android 10 gestures? Or was I not looking there?
_Melkiy_ said:
No Android 10 gestures? Or was I not looking there?
Click to expand...
Click to collapse
Apparently not, I'm just using the 3 button as I still can't get used to full gestures lol
_Melkiy_ said:
No Android 10 gestures? Or was I not looking there?
Click to expand...
Click to collapse
JS.zip said:
Apparently not, I'm just using the 3 button as I still can't get used to full gestures lol
Click to expand...
Click to collapse
No Pixel Launcher! (EDIT: I am using gestures, see below.) There are some apps that add that capacity. I'm trying to restore the Pixel Launcher with TiBu but haven't been successful yet.
---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------
@kkjb gives info about how to add it back above but I haven't figured that out yet either. I've been having problems installing apk's on 10. I get a "Sorry, no application available"
EDIT: ES File Explorer and perhaps other file managers that haven't been updated to work with 10 don't work. Amaze or the native file manager works, as do others I expect that are designed to work with the scoped memory framework of 10.
------------------------------------------------------
_Melkiy_ said:
...
Click to expand...
Click to collapse
JS.zip said:
...
Click to expand...
Click to collapse
Well, I have to correct myself! I'm using gestures now but I don't remember how I got it or selected it or whatever. When I figure it out, I'll post it.
Is anybody else seeing this when searching settings?
Any chance for an updated version of this?
This is some freakin' cool $hit!!!
What are the main advantages of this rom over stock android 10?
nokiasatyam said:
What are the main advantages of this rom over stock android 10?
Click to expand...
Click to collapse
Research the differences between AOSP, Code Aurora (CAF) and stock Google. Then with custom roms that are built either from stock or aosp, you'll know what to expect. I'll give a quick overview for you.
AOSP is pure Android. While heavily influenced by Google, it's 100% open source and free to modify. It includes no extra apps, no Google, nothing. The only thing on this rom that says Google is the search bar on the home screen, and I'm fairly sure that's only for dev testing because there's not even a browser really, it's just AOSP's webview. AOSP is the cleanest, simplest system you can get. It should have the least bugs and also the least features. It literally doesn't include a browser. CAF is basically optimized AOSP. It's Qualcomm directed so optimizations can be done on the Snapdragon chips. You will rarely see AOSP without CAF code because no one likes an unoptimized phone. Qualcomm produces optimization code because they make the chips, Google adds Android features like gesture navigation because Google is on the software side, and the end result is stock Android. The main advantage to AOSP is a clean system. The only Google apps on there are the ones you install yourself. This is my preferred method since I like to add things one at a time, and if there are any issues I remove the last thing I added. There's no extra background stuff I have to sort through if I have an app crash or battery drain. The counter is that I get zero extra features, I must add them all myself. On this rom for example, gestures must be activated (the apks are in fact present in the system), no pixel launcher, no play store, no Find My Device, nothing extra. OP included a vendor image for Mind the Gapps. These are open source implementations of Google apps, but the apps themselves still use Google's proprietary code. Necessary to still use proprietary code if you want everything to work like stock. Open Gapps is one I've used a lot, still fits my preference because it only installs base Google framework, allowing you to choose what Gapps you install. For example, Play Music which I never use is typically just taking up space on my phone and can't normally be uninstalled. With Open Gapps, it's not installed by default in the pico package, and I can install and uninstall play music at will. This is base knowledge for installing custom roms. If you just want things to work, stick to stock. But I've found I get better battery life with AOSP/ Lineage and minimal Gapps. Lineage has more bugs than stock. Pros and cons, pick your poison.
OP- Not underwhelmed, I'm overjoyed. This is exactly what I wanted. Nice and clean, the only extras are what I personally add. My tether options are greyed out, does anyone know how to enable them? It can't be a rom issue, everything works. Just a build.prop edit I'm assuming?

Categories

Resources