A lot of people running Cyanogenmod, and other custom AOSP-based ROMs would like to have the gallery that ships with the Nexus devices. This zip will replace your gallery (Gallery2.apk) with the stock Google gallery (GalleryGoogle.apk). This will give you Picasa sync and the ability to view Photospheres on Nexus 7 devices, and take Photospheres on devices with a rear camera! This mod also includes an addon.d script.
What is addon.d?
On some ROMs, like Cyanogenmod, there are scripts in /system/addon.d that run during a ROM update or flash. They can backup and restore system apps (like Gapps), or perform many other functions. This mod includes an addon.d script, so the mod is not lost during a ROM update! If your ROM doesn't support addon.d, this mod should still flash properly, but you won't benefit from addon.d.
Tested and Confirmed to work on:
CyanogenMod 10.2
Install Instructions:
- Boot into recovery
- Flash Install zip
- Reboot
Downloads:
Install-GoogleGallery-1.6.zip
Changelog:
Code:
1.6 - 11/8/13
- Added some missing libs
1.5 - 11/8/13
- Updated, based on 4.4
1.4 - 9/15/13
- Removed device checks (so it will work on virtually any device), added missing libs, and renamed mod from Install-Nexus7Gallery to Install-GoogleGallery
1.3 - 7/25/13
- Updated, based on 4.3 (JWR66V)
1.2 - 3/3/13
- Updated liblightcycle.so from 20130301 gapps (since Nexus 7 can't take photospheres, this file probably doesn't matter but I updated it anyway)
1.1 - 2/20/13
- Added tilapia (Nexus 7 3G) support
1.0 - 2/20/13
- Initial release, based on 4.2.2 (JDQ39)
DISCLAIMER:
This mod involves editing system files. Use at your own risk! Also please don't forget, before you report ROM related bugs in the ROM developer thread, you should remove this mod to make sure the issue is not caused by this mod!
Re: [MOD][addon.d] Stock Gallery w/ Picasa Sync
Will this work on any device running cm 10.1?
Sent from my Nexus 7 using Tapatalk HD
counterfeit187 said:
Will this work on any device running cm 10.1?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Sorry, no, it specifically checks to see if your device is a grouper. Hmm, you got me thinking, maybe I need to add tiliapia in the device check.
What device are you wondering about?
Re: [MOD][addon.d] Stock Gallery w/ Picasa Sync
rmkilc said:
Sorry, no, it specifically checks to see if your device is a grouper. Hmm, you got me thinking, maybe I need to add tiliapia in the device check.
What device are you wondering about?
Click to expand...
Click to collapse
Samsung epic4g :-\
Sent from my SPH-D700 using Tapatalk 2
counterfeit187 said:
Samsung epic4g :-\
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
It would be easy to remove the device checks, so it installs on anything, but no guarantees photosphere or the gallery would work.
Zip updated, now supports tilapia.
rmkilc said:
Zip updated, now supports tilapia.
Click to expand...
Click to collapse
I vote for removing device checks, maybe with a warning. Could it set aside the original as a .bak and have a revert script? I know that's a lot to ask and if I could I would offer help to write it
My download links will be broken for awhile. Goo.im is having issues, and they are working on it. More information can be found here: https://plus.google.com/103016236037938342074/posts/iWu73keEHtW
In the meantime, if you need a file ASAP, PM me.
Install on htc desire Z
How can I install it on my phone (in case it may works...)? Do I have to install the tilapia version or the grouper?
Thanks
I PM you because goo isn't working.
Sent from my Nexus 7 using xda premium
---------- Post added at 08:48 AM ---------- Previous post was at 08:46 AM ----------
Rafosky said:
I PM you because goo isn't working.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
rmkilc said:
My download links will be broken for awhile. Goo.im is having issues, and they are working on it. More information can be found here: https://plus.google.com/103016236037938342074/posts/iWu73keEHtW
In the meantime, if you need a file ASAP, PM me.
Click to expand...
Click to collapse
Yep.. I need the file
Sent from my Nexus 7 using xda premium
Just installed this zip and get a force close every time I try to save a pic from Picasa or share one anyone else have this problem?
Sent from my Nexus 7 using Tapatalk HD
Force close or message warning when try to share/pick photo.
INC 4G
I'd like to replace the CM 10.1 gallery on my INC 4G so I can get Google+ image syncing to work. The zip on this thread throws a "grouper" specific device error. Is the talapia version available somewhere?
Thanks.
nproszkow said:
I'd like to replace the CM 10.1 gallery on my INC 4G so I can get Google+ image syncing to work. The zip on this thread throws a "grouper" specific device error. Is the talapia version available somewhere?
Thanks.
Click to expand...
Click to collapse
This zip checks for both grouper and tilapia (as of version 1.1). If you are wanting to flash this on a device other than grouper or tilapia, you will have to modify the zip.
rmkilc said:
This zip checks for both grouper and tilapia (as of version 1.1). If you are wanting to flash this on a device other than grouper or tilapia, you will have to modify the zip.
Click to expand...
Click to collapse
I have problems whit goo.im, mirror please?
Enviado desde mi Nexus 7
jamm513 said:
I have problems whit goo.im, mirror please?
Enviado desde mi Nexus 7
Click to expand...
Click to collapse
PM sent.
Sent from my Nexus 4 using Tapatalk 2
Borrowing your scripts, please
I was considering trying to make something like this (an addon.d script) for the Camera and Gallery for Samsung Galaxy S3. I hate having to reflash the a patched camera zip after every CyanogenMod Nightly build.
I'm not terribly worried about device checks because I'd only be trying it for myself on one specific device initially, so I imagine it is the 77-gapps-tilapia.sh script that I'd need to look at to make edits for my purposes. It appears that there are two apks (GalleryGoogle.apk and GmsCore.apk) and three libs (libjni_filtershow_filters.so, libjni_mosaic.so, and liblightcycle.so) necessary to make the camera/galler work on the Galaxy S3.
Your script begins with:
list_files() {
cat <<EOF
app/GalleryGoogle.apk app/Gallery2.apk
lib/liblightcycle.so
EOF
}
Would it be as simple as changing this to:
list_files() {
cat <<EOF
app/GalleryGoogle.apk app/GmsCore.apk
lib/libjni_filtershow_filters.so lib/libjni_mosaic.so lib/liblightcycle.so
EOF
}
This is my first time trying to do something like this but I could see it being useful for a lot of people--the galaxy S3 is a popular phone on many carriers. Anyone willing to give me a hand?
counterfeit187 said:
I was considering trying to make something like this (an addon.d script) for the Camera and Gallery for Samsung Galaxy S3. I hate having to reflash the a patched camera zip after every CyanogenMod Nightly build.
I'm not terribly worried about device checks because I'd only be trying it for myself on one specific device initially, so I imagine it is the 77-gapps-tilapia.sh script that I'd need to look at to make edits for my purposes. It appears that there are two apks (GalleryGoogle.apk and GmsCore.apk) and three libs (libjni_filtershow_filters.so, libjni_mosaic.so, and liblightcycle.so) necessary to make the camera/galler work on the Galaxy S3.
Your script begins with:
list_files() {
cat <<EOF
app/GalleryGoogle.apk app/Gallery2.apk
lib/liblightcycle.so
EOF
}
Would it be as simple as changing this to:
list_files() {
cat <<EOF
app/GalleryGoogle.apk app/GmsCore.apk
lib/libjni_filtershow_filters.so lib/libjni_mosaic.so lib/liblightcycle.so
EOF
}
This is my first time trying to do something like this but I could see it being useful for a lot of people--the galaxy S3 is a popular phone on many carriers. Anyone willing to give me a hand?
Click to expand...
Click to collapse
I'm not 100% familiar with the extra files required on the GS3, but I think you want this:
Code:
list_files() {
cat <<EOF
app/GalleryGoogle.apk app/Gallery2.apk
app/GmsCore.apk
lib/liblightcycle.so
lib/libjni_filtershow_filters.so
lib/libjni_mosaic.so
EOF
}
Each line handles one file. If only one file is listed on a line, it will carry it through. If two files are listed with a space between them, it will replace the second file with the first file. For example, in my script, we want GalleryGoogle.apk to replace Gallery2.apk. The files must be the entire path within /system with no leading forward slash. Make sense?
Can't save or share
When I try to share or save an image the apps closes or tells you that it can't use the image
Please FIX
Im on Smootrom 5.1
Hi!
Worked OK but now I want to revert the changes. What if I want to go back to the original version?
Thanks,
Related
In case anyone is having trouble finding toro as a device target when trying to build from the list of targets from the 'lunch' command... Toro didn't show up in the list but I was able to manually specify it rather than selecting a numeric option.
Devs probably know that works, but amateurs like myself might benefit from that tidbit. Jellybean seems to be building OK for me now.
EDIT: I was asked what I did, more specifically, so I'll put that here in op:
Rather than enter a numeric choice, I entered 'full_toro-userdebug'. Apparently this was a valid response and the build proceeded.
Mind explaining how you manually selected it?
keith.mcintyre26 said:
Mind explaining how you manually selected it?
Click to expand...
Click to collapse
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.
question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?
spunks3 said:
question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?
Click to expand...
Click to collapse
It's not as 'polished'. There are no gapps, the dictionary is not complete (need a version from a factory image/rom), there are extra keyboards (Japanese?), maybe a couple other oddities as compared to a stock ROM. It will certainly be more capable that porting a gsm rom to toro, that's for sure .
mmuzzy said:
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.
Click to expand...
Click to collapse
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium
keith.mcintyre26 said:
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You're very welcome. Happy flashing.
I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
mmuzzy said:
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
Click to expand...
Click to collapse
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was actually trying to pull it before Google was finished so it hasn't been that long.
Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?
anton2009 said:
Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?
Click to expand...
Click to collapse
Lol!
Sent from my Galaxy Nexus using Tapatalk 2
phydo said:
Lol!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this
Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?
cdrshm said:
Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?
Click to expand...
Click to collapse
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!
CPCookieMan said:
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!
Click to expand...
Click to collapse
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.
i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
mwalt2 said:
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.
Click to expand...
Click to collapse
cdrshm said:
i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
Click to expand...
Click to collapse
For future reference, what he's referring to is the extract-files.sh script included in the CM source. If you cannot find the proprietary binaries for a certain device you wanna build for, plug in the phone via usb, cd to the directory with the script and execute the command.
anton2009 said:
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this
Click to expand...
Click to collapse
I also got version 4.0.9.99.999.9999.99999 when I synced to the master branch. Thanks for mentioning the workaround to sync with 4.1.1_r1 .
Did you figure out if it's a problem to sync 4.1.1 into a directory that's already synced with master (4.0.9.99...)?
--------------------------------
Update: I think I can answer this question based on JBQ's response:
https://groups.google.com/d/msg/android-building/rtH5ZbJC7qU/-N1lr9MqexYJ
"You can also switch in place: just run "repo init -b <new_manifest_branch>; repo sync" in your existing client."
Sounds like syncing to a new branch in the same working directory should work just fine.
READ THIS ENTIRE POST PLEASE
PLEASE PROCEED TO USE THE 4.3 VERSION LOCATED Android 4.3 JWR66V
UPDATED ROM IS MUCH MORE STABLE AND BATTERY LIFE IS GREAT.
Thanks to everyone for testing/using this one until now
This ROM comes from I9505 variant.
Luckily the only thing you will need to do is apply Loki patch if you require it for other ROMS.
If you are a CAN variant you can simply install the ROM with no other issues or steps.
IMPORTANT
User reports suggest that battery life is much better as well as working google wallet in the odex version, root should work for both.
Google Play 4.1.10 : Please manually update Google Play to prevent gps/maps battery drain, download apk and install as usual
There are two FactoryKeystring.apk's included and actively used by Android System, one is hidden and one is in System/app, removing one seems to improve battery life (must have root)
Do NOT change Dpi you will loose root and you will loose wifi. You have been warned.
WARNING
As always, i'm not responsible for your phone blowing up or bricking. Hell this is completely pre-release software that Google hasn't even published yet so you better be sure you're ready to take the plunge and accept that anything can happen and i assume no responsibility. this is all your choice.
System Details
Android version: 4.3
Build ID: JWR66N
PDA: I9505GUEUBMFP
CSC: I9505GXARBMFP
Build Date: 26 June 2013
Changelist: 968842
DOWNLOADS
Odexed & DevHost Mirror
Deodexed & DevHost Mirror
--
LokiDoki Only for U/S variants - CAN variants do not download.
Chainfires Root Guide When doing this please flash full rom and let boot then reboot back to recovery and install this zip
HOW TO FOR CAN VARIANTS
1. Copy ROM (Odex or Deodex) to your internal SD Card
2. Enter Recovery (Power + Volume Up + Home)
3. Do a Wipe/Factory Reset (Necessary due to new Android version)
4. Flash ROM
5. Reboot your device!
HOW TO FOR US VARIANTS
1. Copy ROM (Odex or Deodex) to your internal SD Card
2. Enter Recovery (Power + Volume Up + Home)
3. Do a Wipe/Factory Reset (Necessary due to new Android version)
4. Flash ROM
5. Flash LokiDoki don't rely on a recovery with auto loki
5. Reboot your device!
SCREENSHOTS
SAMmobile page linked here has screen shots. Its stock AOSP not TW
BENCHMARKS
Antutu // Quadrant \\ 3DS Max
Moved to bottom in attachments to reduce OP size
APPS THAT HAVE ISSUES
1. Apex will FC - Solution, use Nova Launcher or various other ones.
2. DashClock will not work at all.
3. CNN App, Live TV - lets you sign in but when attempting to play a video it gives "this video is not available" error.
4. Tapatalk has been reported to have issues, works fine for me. Test yourself.
5. Titanium Backup seems to be having issues restoring.
EXTRAS || PROBLEMS || BUGS
1. Root Chainfires Root Guide
2. IR Works, Install WatchON if you want
3. Charging is SLOW at first, please give ROM about a day to settle and it will be fine.
4. Battery may also drain faster then normal at first, again please give ROM time to settle.
5. Stock Camera - If you start the camera for the first time, you may get a black screen. close it and wait a minute. Reopen and it will work.
6. Wallet works on Odex, have had mixed reports with Deodex
7. Continue to post feed back about apps having issues so I can update here
WHATS DIFFERENT IN 4.3 FROM 4.2.2?
- Roboto font has been cleaned up see here
- "android.hardware.bluetooth_le" listed as a feature in the Android System Info app, suggesting Bluetooth Low Energy support is on-board in Android 4.3. This feature isn't listed on the Google edition GS4 review unit running Android 4.2.2
- Bluetooth tethering is present in the 4.3 ROM, while it's absent (bizarrely) in the 4.2.2-based GS4 GE unit.
- A new checkbox under Advanced Wifi settings allows Google's location service to scan for Wifi networks even when Wifi is turned off and not being used for wireless networking (likely part of Google's new approach to battery-friendly location services)
- Multiple options under "Monitoring > Profile GPU Rendering," as seen in this Google I/O video.
This lets you view a graphical representation of the time taken to generate a frame, and see whether you're hitting the 60 frames per second target or not. This should help devs create more buttery apps.
- New debug options for the new non-rectangular clipping feature. This is a new graphical capability for devs in Android API level 18.
- New option to "Use experimental WebView" (this likely changes the browsing engine used to handle websites within apps, but has yet to be confirmed.
- There is now a button that lets you "Revoke USB debugging authorization." This deletes the RSA key generated for USB debugging authorization from the phone itself, previously you had to do this from the computer side.
- Pressing menu in the phone app, lets you now add two-second pauses in your dialing string (denoted by a comma) or longer waits (denoted by a semicolon.)
- In the Settings of the phone app, you can now enable dial-pad autocomplete and change DTMF (dual-tone, multi-frequency) tone lengths.
- Of course there's the new camera app.
- Long, multi-word SSID names now wrap properly down to a second line in the quick-settings pulldown.
- When you take a screenshot and share it via email, the Subject field is automatically populated with the date and time of the shot.
Thanks to :
SAMmobile for posting Jelly Bean 4.3
A$$h4t for providing the LokiDoki link
mr_blanket fo providing a link to updated Google Play apk to fix some battery drain.
AndroidPolice : their article showing the Roboto font changes/clean up - Found here
AndroidCentral : For their hands on article describing some changes - found here
Chainfire for getting Root!
But you cant root this?
SysAdmNj said:
But you cant root this?
Click to expand...
Click to collapse
Not sure, haven't tried.
Make a NANDROID then download and install and try to root like you would anything, if it doesn't work then reboot in to recovery and restore your NANDROID.
Downloading now......
kylecore said:
Not sure, haven't tried.
Make a NANDROID then download and install and try to root like you would anything, if it doesn't work then reboot in to recovery and restore your NANDROID.
Click to expand...
Click to collapse
I already had the leak but havent tried it yet as I tried GE yesterday and it didnt go too well. Went back to Omega7, will try this as soon as I hear you can root.
Do we need the AOSP kernel or the Touchwiz kernel for the AT&T I-337?
oldblue910 said:
Do we need the AOSP kernel or the Touchwiz kernel for the AT&T I-337?
Click to expand...
Click to collapse
I was wrong.
Sent from my GT-I9505G using xda premium
oldblue910 said:
Do we need the AOSP kernel or the Touchwiz kernel for the AT&T I-337?
Click to expand...
Click to collapse
Please see the op where it says in the second sentence NOT to use a TW kernel, since this is stock AOSP you need an AOSP kernel.
clyon3 said:
TW..... Some say it won't boot and you will lose root.
Click to expand...
Click to collapse
Wrong, completely wrong. It will just need to be a pre-loki'd kernel (i've posted a link to one in the OP)
kylecore said:
Please find the correct kernel for your phone that is NOT a TW kernel in the various threads before attempting to flash.
Click to expand...
Click to collapse
kylecore said:
Please see the op where it says in the second sentence NOT to use a TW kernel, since this is stock AOSP you need an AOSP kernel.
Wrong, completely wrong. It will just need to be a pre-loki'd kernel (i've posted a link to one in the OP)
Click to expand...
Click to collapse
So an aosp att kernel would work?
Sent from my SGH-I337 using Tapatalk 2
Gonna attempt to port this to ATT S4
Sent from my SGH-I337 using Tapatalk 2
mrakifa said:
So an aosp att kernel would work?
Click to expand...
Click to collapse
Yes in fact try the one in the OP it links to a thread where the AOSP one is.
Anthony04x said:
Gonna attempt to port this to ATT S4
Click to expand...
Click to collapse
Theres nothing to port, just flash an ATT kernel of choice immediately after the rom and its fine.
kylecore said:
Yes in fact try the one in the OP it links to a thread where the AOSP one is.
Theres nothing to port, just flash an ATT kernel of choice immediately after the rom and its fine.
Click to expand...
Click to collapse
All you need is loki doki the stock kernel works wifi, camera, bluetooth and lte no need to flash any other kernels
Sent from my GT-I9505G using Tapatalk 2
mastergrillo said:
All you need is loki doki the stock kernel works wifi, camera, bluetooth and lte no need to flash any other kernels
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I can also verify this. LokiDoki makes the stock kernel work just fine.
Right then, downloaded ROM and AOSP kernel provided in OP. Wiped, flashed, wifi is a no go for me and same as camera, totally borked (black screen). LTE works...everything else seems to work.
mastergrillo said:
All you need is loki doki the stock kernel works wifi, camera, bluetooth and lte no need to flash any other kernels
Click to expand...
Click to collapse
oldblue910 said:
I can also verify this. LokiDoki makes the stock kernel work just fine.
Click to expand...
Click to collapse
Thanks, anyone have a link to the thread for that? I can update the OP for people.
I'm a CAN variant so i've never touched anything that even mentions Loki
TheSmokingAndroid said:
Right then, downloaded ROM and AOSP kernel provided in OP. Wiped, flashed, wifi is a no go for me and same as camera, totally borked (black screen). LTE works...everything else seems to work.
Click to expand...
Click to collapse
If you're on ATT see the above and use stock kernel
Those that installed it can you confirm that root works?
Sent from my SGH-I337 using xda premium
sabre31 said:
Those that installed it can you confirm that root works?
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
No root for this yet
Sent from my GT-I9505G using Tapatalk 2
sabre31 said:
Those that installed it can you confirm that root works?
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
I don't believe anyone has figured out root yet.
+1 on loki doki for ATT I337
Download loki-doki zip here: http://tau.shadowchild.nl/attn1/?p=483
A$$h4t said:
I don't believe anyone has figured out root yet.
+1 on loki doki for ATT I337
Download here: http://tau.shadowchild.nl/attn1/?p=483
Click to expand...
Click to collapse
does flashing it from the OUDHS Recovery work too? (it auto-lokis kernels)
and another question
for the google edition 4.2 I had to flash the Ktoon TW Kernel. Why AOSP for this one?
thanks!
jhong91 said:
does flashing it from the OUDHS Recovery work too? (it auto-lokis kernels)
and another question
for the google edition 4.2 I had to flash the Ktoon TW Kernel. Why AOSP for this one?
thanks!
Click to expand...
Click to collapse
Thats the recovery im using and it didnt do for me i had to use loki doki
Sent from my GT-I9505G using Tapatalk 2
For those who prefer open source builds, rather than "Factory Images", here is a zip which is a stock, AOSP 4.3 build, straight from source. Why post this when anyone could make it? Well, it seems Google messed up their binary drivers, so it took me a little while to fix them, and fix the problems and get the ROM booting (they put the wrong mali GLES driver in their blob package).
Anyway, I have fixed that, and made it build successfully, so without futher ado, an AOSP (no google proprietary apps etc) build of 4.3 for the Nexus 10. The fixed vendor blobs are available at https://github.com/pulser/vendor_samsung_manta for anyone wanting to build themselves, and all can be verified, as they came from the "Factory Image" of 4.3 for the Nexus 10.
This is a pure AOSP build, there is no boot animation or any other "Google" things - just a plain, pure, AOSP build.
Enjoy, and this can be rooted using Chainfire's current 4.3 root method using SuperSU, which is detailed at https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Feel free to use, share, re-use, distribute, copy, paste, mirror, ignore, root, tweak, patch or mod. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this
Tested:
Wi-Fi
Bluetooth
GPS
Auto rotation
Accelermeter
Magnetic Field Sensor
Brightness Sensor (and Autobrightness)
Barometer
Seemingly not working:
Proximity sensor (not detected, but apparently has one)
Download:
http://goo.im/devs/pulser/Nexus10
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
duarian said:
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Stock image isn't the AOSP?
I am not worrying.
Thanks OP.
duarian said:
Hmmm...I'm co cerned what you said about they put the wrong Mali driver in. What does this effect for those of us who flashed the stock image from the website?..
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Nothing to worry about. I took the RIGHT driver from the factory image (stock image).
The AOSP release they made had wrong blobs, I rectified it with the correct files from the stock image.
I missed a blob:
https://github.com/pulser/vendor_samsung_manta/commit/4c534c24407a163bc16bfa24cb769aef7ab9ebd3
Push to /system/vendor/lib/
pulser_g2 said:
I missed a blob:
https://github.com/pulser/vendor_samsung_manta/commit/4c534c24407a163bc16bfa24cb769aef7ab9ebd3
Push to /system/vendor/lib/
Click to expand...
Click to collapse
How do we download the file/blob please?
Never downloaded anything from Github before...
pulser_g2 said:
For those who prefer open source builds, rather than "Factory Images", here is a zip which is a stock, AOSP 4.3 build, straight from source. Why post this when anyone could make it? Well, it seems Google messed up their binary drivers, so it took me a little while to fix them, and fix the problems and get the ROM booting (they put the wrong mali GLES driver in their blob package).
Anyway, I have fixed that, and made it build successfully, so without futher ado, an AOSP (no google proprietary apps etc) build of 4.3 for the Nexus 10. The fixed vendor blobs are available at https://github.com/pulser/vendor_samsung_manta for anyone wanting to build themselves, and all can be verified, as they came from the "Factory Image" of 4.3 for the Nexus 10.
This is a pure AOSP build, there is no boot animation or any other "Google" things - just a plain, pure, AOSP build.
Enjoy, and this can be rooted using Chainfire's current 4.3 root method using SuperSU, which is detailed at https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
Feel free to use, share, re-use, distribute, copy, paste, mirror, ignore, root, tweak, patch or mod. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this
Tested:
Wi-Fi
Bluetooth
GPS
Auto rotation
Accelermeter
Magnetic Field Sensor
Brightness Sensor (and Autobrightness)
Barometer
Seemingly not working:
Proximity sensor (not detected, but apparently has one)
Download:
http://goo.im/devs/pulser/Nexus10
Click to expand...
Click to collapse
Is this why the latest version supported for manta is 4.2.2r1 (according to this) while everything else is 4.3xx?
Explains why I can't get a flashable build.
This is why I stick to factory images.
ridobe said:
Is this why the latest version supported for manta is 4.2.2r1 (according to this) while everything else is 4.3xx?
Explains why I can't get a flashable build.
Click to expand...
Click to collapse
It may well be, but the factory image is available.
But some of us don't want GApps, and don't want binary parts (save for the necessary evil of drivers), which is where AOSP builds come in.
pulser_g2 said:
It may well be, but the factory image is available.
But some of us don't want GApps, and don't want binary parts (save for the necessary evil of drivers), which is where AOSP builds come in.
Click to expand...
Click to collapse
Thanks. I like to build for myself but couldn't figure out why I couldn't flash successfully. Upon further investigation it appears that it is not supported (yet) in aosp. I'm running the factory images for now instead. However, this evening I'm going to flash this.
I just want to make sure. This wont wipe my internal hard drive. First time i flashed the new 4.2 i lost everything and cant backup anything as of now because i am outta town the whole summer.. Plz if anybody can confirm
Sent from my Nexus 10 using Tapatalk HD
BabyHuey said:
I just want to make sure. This wont wipe my internal hard drive. First time i flashed the new 4.2 i lost everything and cant backup anything as of now because i am outta town the whole summer.. Plz if anybody can confirm
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am not aware of anything to deliberately wipe /data, but I strongly suggest you don't flash this, unless you are willing to lose things? Why? because I didn't test every possible situation that could come up. I also didn't CHECK that /data remained...
So perhaps take the OTA (if you're on stock)? Or just hang off? It's nothing hugely special in my opinion.
pulser_g2 said:
I also didn't CHECK that /data remained...
Click to expand...
Click to collapse
It does, I flashed it.
Would still like to know how to get those missing blobs...
stonebear said:
It does, I flashed it.
Would still like to know how to get those missing blobs...
Click to expand...
Click to collapse
So nothing will be wiped?
Sent from my Nexus 10 using Tapatalk HD
BabyHuey said:
So nothing will be wiped?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
My data remained, but I would be concerned if you took a chance on my say so and something went wrong. I was ok but maybe you wouldn't be for some reason.
Sent from my Nexus 7 using Tapatalk 4 Beta
stonebear said:
It does, I flashed it.
Would still like to know how to get those missing blobs...
Click to expand...
Click to collapse
Which ones? The blobs are in the github link and came from the factory image. I'm not aware of any missing ones.
pulser_g2 said:
Which ones? The blobs are in the github link and came from the factory image. I'm not aware of any missing ones.
Click to expand...
Click to collapse
I don't know how to download them. Are they downloadable?
I suppose if I could understand the page I would know which ones to take from the factory image...noob, sorry.
Is it just "libRSDriverArm.so"?
http://d-h.st/aPi
4.3 gapps
Sent from my AOSP on Manta using Tapatalk HD
Thanks pulser_g2 for adding the correct binary blobs! Glad I'm not completely insane like I thought I was, I too noticed that Google had forgotten to provide the correct graphics driver binaries so I tried building 4.3 with the 4.2.2 graphics binaries and it not surprisingly didn't boot past the Google logo. Glad we could get this fixed :good:.
stonebear said:
I don't know how to download them. Are they downloadable?
I suppose if I could understand the page I would know which ones to take from the factory image...noob, sorry.
Is it just "libRSDriverArm.so"?
Click to expand...
Click to collapse
Sure, that is the only "blob" I am aware I forgot. The N10 supposedly supports Bluetooth 4 (LE), but I have no idea how to test it, as I don't have any Bluetooth 4 LE devices. Can anyone test that? I will update the system.img today for you to make it easier It was only one blob I missed, and it only affects using front facing camera I believe.
Disclaimer: I take no responsibility for bad things that may occur as a result of flashing this.
NOTE: If coming from 10.1, make a back up first as you will not be able to flash back to 10.1 unless you factory reset
These are Unofficial CM 10.2 builds for the Verizon Galaxy Note 10.1
Prereq: Unlocked Bootloader
It is recommended to flashed this in CWM .
Source: http://github.com/sbrissen
Instructions:
-Download and copy rom to sdcard
-Download and copy gapps to sdcard (make sure they are for 4.3!)
-Reboot into recovery (CWM)
-Flash rom
-Flash gapps
-Wipe data/cache
-Reboot
Known Bugs:
-May need to get a gps lock on stock before switching to CM in order for gps to work
-BT voice search
- Graphical glitches (i.e. black screens) - will require new Mali graphic blobs
- No screenshot or anything that relies on screenshots - will require new Mali graphic blobs
[8/1]ROM: http://www.androidfilehost.com/?fid=23060877489997664
Changes:
- Initial Release
[8/8]ROM: http://www.androidfilehost.com/?fid=23060877489998603
Changes:
- Fix Screenshots (framework hack)
- CM Upstream Changes
sbrissen said:
Disclaimer: I take no responsibility for bad things that may occur as a result of flashing this.
NOTE: If coming from 10.1, make a back up first as you will not be able to flash back to 10.1 unless you factory reset
These are Unofficial CM 10.2 builds for the Verizon Galaxy Note 10.1
Prereq: Unlocked Bootloader
It is recommended to flashed this in CWM .
Source: http://github.com/sbrissen
Instructions:
-Download and copy rom to sdcard
-Download and copy gapps to sdcard (make sure they are for 4.3!)
-Reboot into recovery (CWM)
-Flash rom
-Flash gapps
-Wipe data/cache
-Reboot
Known Bugs:
-May need to get a gps lock on stock before switching to CM in order for gps to work
-BT voice search
- Graphical glitches (i.e. black screens) - will require new Mali graphic blobs
- No screenshot or anything that relies on screenshots - will require new Mali graphic blobs
[8/1]ROM: http://www.androidfilehost.com/?fid=23060877489997664
Changes:
- Initial Release
Click to expand...
Click to collapse
I got a built prop error like no sch i925 stuff....was not able to flash it...
what recovery did you use? also have you tried redownloading?
can anyone else confirm the same result?
Sent from my SCH-I605 using xda app-developers app
Where can we download Gapps for 4.3? I didn't see them on goo.im.
Edit: Ah just found this http://forum.xda-developers.com/showthread.php?t=2378992
sbrissen said:
what recovery did you use? also have you tried redownloading?
can anyone else confirm the same result?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I have cwm installed, i will try again...but one question first: do I have to have an american kind of galaxy note 10.1 (Verizon) or can it be installed on any kind of international Hardware? maybe thats my issue?
Edit1: redownloaded, still not working, same error
Also i have been wondering this. Is it bad to format preload? I did so by accident :/
W00fah said:
Also i have been wondering this. Is it bad to format preload? I did so by accident :/
Click to expand...
Click to collapse
No Problem, if you format preload.
Grtz Rongogo
GT-N8000
With Rongogorom
GeneralSmart said:
I have cwm installed, i will try again...but one question first: do I have to have an american kind of galaxy note 10.1 (Verizon) or can it be installed on any kind of international Hardware? maybe thats my issue?
Edit1: redownloaded, still not working, same error
Click to expand...
Click to collapse
Yes you will need the vzw note 10.1, that's why the assert is failing. Its a fail safe so a rom isn't flashed on a device its not meant for.
Sent from my GT-N5110 using xda app-developers app
So far this is so much faster than stock ROM. I'm still testing if 4g is any weaker.
Thanks so much for this work. Its like having a brand new tablet with latest and greatest!
Sent from my SCH-I925 using xda premium
Since there isn't a stock image for the device, would a cwm backup be suitable in rolling back should I experience any issues?
zerogauge said:
Since there isn't a stock image for the device, would a cwm backup be suitable in rolling back should I experience any issues?
Click to expand...
Click to collapse
Yes
Sent from my GT-N5110 using xda app-developers app
Yes, cwm will restore your saved backup.
But so far, I'm not sure I will need to. This is blazingly faster..
Sent from my SCH-I925 using xda premium
Awesome, thanks for the replies. Flashed this morning and I'm now setting everything up. So far I'm loving it though. Quick boot times and overall it feels a lot leaner. Thanks for the rom and the support. Been following you since the fascinate days.
*Edit* Ran into a redraw issue or something with TouchdownHD. I posted a video at http://youtu.be/dz5gzv6Sdco is there a setting available that might fix this? I've tried re-installing the application and I still get the same issue.
This rom is just like lightning...thanks sbrissen!
Sent from my GT-I9300 using Tapatalk 2
Will this work on n8010?
Quick question,can this be installed on the 8013, is there any way for you to make for it. Anyway thanks for making great roms for our devices.
Sent from my GT-N801x using Tapatalk 4
xlamian said:
Quick question,can this be installed on the 8013, is there any way for you to make for it. Anyway thanks for making great roms for our devices.
Sent from my GT-N801x using Tapatalk 4
Click to expand...
Click to collapse
Try it and find out keep us posted.
Nandroid.
Edit: Just tried it. Does not work It checks to make sure you are on the correct device, as stated on the first page
LexusBrian400 said:
Try it and find out keep us posted.
Nandroid.
Edit: Just tried it. Does not work It checks to make sure you are on the correct device, as stated on the first page
Click to expand...
Click to collapse
You could try what I did and unzip, swap metainf folder from 8013 installer go through the build.prop file with notepad ++ and change tablet type from Verizon to n8013 and see what happens! Good luck :laugh:
smegg said:
You could try what I did and unzip, swap metainf folder from 8013 installer go through the build.prop file with notepad ++ and change tablet type from Verizon to n8013 and see what happens! Good luck :laugh:
Click to expand...
Click to collapse
I will give it a try once I get back home...next week,can't afford to be without it while travelling with the kid.
Sent from my GT-N801x using Tapatalk 4
xlamian said:
I will give it a try once I get back home...next week,can't afford to be without it while travelling with the kid.
Sent from my GT-N801x using Tapatalk 4
Click to expand...
Click to collapse
Hey I found this too, wish I had it before instead of just shooting in the dark...lol
http://forum.xda-developers.com/showthread.php?t=2179629
Now we have a fully working (?) cm11... the problem is that there are a lot of gapps packages and no one is "the final" one...
The point is, why we must release updated gapps every time google release new stuff... when there are other people that are already doing that?
The answer is: gapps packages for other phones break panorama on maguro
So I think that would be a good thing if I create a zip package with ONLY GOOGLE CAMERA for maguro. And i created it, picking the necessary files from dhacker29 (thanks!) 20131207 gapps.
So... WHAT DO YOU NEED to have a fully working cm11?
∗ = recommended
1) ROM
Official CM11 nightlies --- changelog ∗
PlayfulGod CM11 (may include addition features!)
2) GAPPS
Nexus 5 gapps (Standard or Core) ∗
ParanoidAndroid gapps
CM gapps
3) KERNEL (optional)
Mpokang_kernel-v10_1080p --- info
4) PANORAMA AND MMS VIDEO FIX
Panorama and mms video fix v4 (~0.4mb) by Suxsem
INSTALL IN THIS ORDER:
READ NOTES BELOW
WIPE DATA IF YOU ARE NOT YET ON CM11
FLASH ROM
FLASH GAPPS
FLASH KERNEL (optional)
FLASH FIX PACKAGE
NOTES
If you get errors while flashing be sure to be on latest recovery... you can use this one: TWRP
Not all gapps packages include Google camera! (for example Nexus 5 Core gapps doesn't include it)
If you have chosen a gapps package that doesn't include it, you can download it from here and flash after gapps: Nexus 5 Google camera
If you need Face unlock feature download it from here and flash after gapps: Nexus 5 Face unlock
Fix package must be last to flash because some kernels include files that would overwrite the fixed ones
that's it. you will not have any more problems with sound search, panorama, face unlock, play store, ecc ecc... and all this stuff is compatible with ART.
most important thing: I didn't test all this really deep. I just tested with a limited types of configurations (didn't tested with pa gapps nor with cm gapps nor with different kernels ecc ecc), i only tested with PlayfulGod cm11, GApps Standard 4.4.1, mpokang kernel and ART... so please let me know if this works for you (and please test this with PA or CM gapps, also with ART)!
You've made a good start by fixing screenshot glitch..... Wish u luck for such further development!!
A Omni ROM build would be great!!
Sent from my Galaxy Nexus using xda app-developers app
RajatPatel said:
You've made a good start by fixing screenshot glitch..... Wish u luck for such further development!!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
i was jocking about new to android development, i was very active in Acer Liquid development but i'm still new to galaxy nexus, so thanks!
Suxsem said:
i was jocking about new to android development, i was very active in Acer Liquid development but i'm still new to galaxy nexus, so thanks!
Click to expand...
Click to collapse
Lol, take it that way then
Sent from my Galaxy Nexus using xda app-developers app
Thanks mate
Sent from my Galaxy Nexus using Tapatalk 4
I would prefer a minimalistic Gapps package having only those apps which are not available on the Play Store.
Sent from my Galaxy Nexus using Tapatalk
AbhishekS said:
I would prefer a minimalistic Gapps package having only those apps which are not available on the Play Store.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
you can use
GApps Core 4.4.1
20 MB-
Basic syncing stuff-
Playstore-
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=2012857
don't forget to flash my fix after that to have panorama working
Suxsem said:
you can use
from http://forum.xda-developers.com/showthread.php?t=2012857
don't forget to flash my fix after that to have panorama working
Click to expand...
Click to collapse
does that gapps have the google retore (wifi networks and such ) ?
brunobliss said:
does that gapps have the google retore (wifi networks and such ) ?
Click to expand...
Click to collapse
i'm almost sure that yes! anyway if you can test and report here thanks
yeah i will, in fact i'm flashing Playfulgod's rom instead of the official CM11. The latter seems to lag every now and then on the app drawer and desktop
btw: Mpokernel ROCKS \m/
brunobliss said:
yeah i will, in fact i'm flashing Playfulgod's rom instead of the official CM11. The latter seems to lag every now and then on the app drawer and desktop
btw: Mpokernel ROCKS \m/
Click to expand...
Click to collapse
it's really strange because playfulgod should be EXACTLY the same of official cm11, except for screenshot fix that will be in official cm11 from 20131212 anyway, because they are the same rom i think that it is more kind to use playfulgod
waiting for your report about restore!
Flashed CM11 in the right order (ROM > GAPPS(Standart 4.4.1) > MY FIX > mpokang 1080p v10 ).
I'm on ART, but whatsapp doesn't work.. Can't install it.
cubeever said:
Flashed CM11 in the right order (ROM > GAPPS(Standart 4.4.1) > MY FIX > mpokang 1080p v10 ).
I'm on ART, but whatsapp doesn't work.. Can't install it.
Click to expand...
Click to collapse
umh, strange...waiting for other to confirm cause i'm using it right now... can you take a logcat while installing please?
I installed (after factory reset) in that order and now it is stuck at cyanogenmod logo. I will try without the kernel.
Hi. You fixed face unlock? I thought face unlock was working on banks gapps
Enviado do meu Galaxy Nexus através de Tapatalk
Anyone have any idea why someone wouldn't be able to send text messages? I just put cm11 on my buddy's gnex last night, he's telling me today he can receive but can't send. He's on at&t using the default APN, and hangouts. Hard for me to diagnose since I don't have his phone with me
Sent from my Nexus 4 using Tapatalk
Suxsem said:
umh, strange...waiting for other to confirm cause i'm using it right now... can you take a logcat while installing please?
Click to expand...
Click to collapse
So here is the logcat.
bitmovel said:
Hi. You fixed face unlock? I thought face unlock was working on banks gapps
Enviado do meu Galaxy Nexus através de Tapatalk
Click to expand...
Click to collapse
i copied the face unlock files from dhacker29 gapps, i'm not sure that will work without those files, you can try!
cubeever said:
So here is the logcat.
Click to expand...
Click to collapse
i got this line before:
Code:
12-11 21:35:59.390 D/Finsky (7461): [795] 1.packageInstalled: Package install status for "com.whatsapp" is -24
while installing greenify. i discovered that was caused by a bad restoring with ROM TOOLBOX app and i fixed it deleting greenify folder from /data/data and greenify apk from /data/app
can you please try to locate something like com.whatsapp* in /data/data and /data/app and delete it?
or maybe you can try to do a full wipe, unless other users can confirm that they got the same error...
Cor-master said:
Anyone have any idea why someone wouldn't be able to send text messages? I just put cm11 on my buddy's gnex last night, he's telling me today he can receive but can't send. He's on at&t using the default APN, and hangouts. Hard for me to diagnose since I don't have his phone with me
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no idea sorry...
Saint787 said:
I installed (after factory reset) in that order and now it is stuck at cyanogenmod logo. I will try without the kernel.
Click to expand...
Click to collapse
let me know, maybe do a full wipe