Just wondering if anyone else have seen GAPPS for tegra. I have downloaded the signed UPDATE and it works beautifully.
Really appreciate the XDA community for all the help.
http://www.megaupload.com/?d=KMXRDDR3
Thanks. I'll give it a try...
So far, no joy. I installed it, wiped cache, and now get FC's. I will try to work around it, but will probably have to go back to backup.
Good find, though.
flashed fine on cm6. lost sound though. not sure if that is because of this or because of something else. will report back after more research.
i even tried with the newer update 3316 and it works fine. The only problem i had was i updated to the newer market and it started crashing. i flashed 3316 and installed gapps and no problems.
One thing i have done differently though is to put the FRF91 key in the build props before install the GAPPS. It took couple of tries for the market to work properly.
Isn't this the original gapps that we've had for a month, now? I see the Htc stuff in there, which kind of tipped me off.
I actually pulled the Htc stuff and some other things out, back when I used it for TnT Lite.
Well the date signature seems to be recent so i guess it's possible.
roebeet said:
Isn't this the original gapps that we've had for a month, now? I see the Htc stuff in there, which kind of tipped me off.
I actually pulled the Htc stuff and some other things out, back when I used it for TnT Lite.
Click to expand...
Click to collapse
Not sure... but here is a link - they are all listed at the bottom of the page.
http://wiki.cyanogenmod.com/index.php?title=Latest_Version
The file name gives it away. 20101020 obviously means 20th October. So yeah, not new
umar.ranjha said:
i even tried with the newer update 3316 and it works fine. The only problem i had was i updated to the newer market and it started crashing. i flashed 3316 and installed gapps and no problems.
One thing i have done differently though is to put the FRF91 key in the build props before install the GAPPS. It took couple of tries for the market to work properly.
Click to expand...
Click to collapse
3316 + GAPPS work great! thanx!
didn't install the new Market but was able to do Market fix (w/o TI Backup)...
Related
Firon was nice enough to make sweet sweet magic. if im right, this will let you update to DI18 if you are on a custom rom/kernel and it will "do the deed" for you.
Firon said:
Here's a signed update that will not trash your recovery, kernel, or root. You do not need a stock kernel for this update.
It will restore only the required stock files/apps and update your modem, so as long as you're on DI07, it should successfully update.
I tested it already on my own phone, worked great.
This way you don't need to restore a bunch of random files to update.
His thread can be found here
Click to expand...
Click to collapse
Only use the attached .zip if you are fully stock!
so i pulled a copy of the DI07 to DI18 update off of my cache partition. anybody want it to mess with?
*edit*
no changes have been made to it. ill let someone else which more adept skills do what they do best. I simply just got the notification, grabbed it from cache and threw it up here.
*edit2*
gotta be 100% stock (minus clockwork)
simple fix? Flash This before you flash the update.
Would it install on its own? If so throw it up here.
Sent from my SPH-D700 using XDA App
Thanks. Installed just fine.
In regards to the upload speed fix alone (not tested much else yet):
DL UL
65 101
294 241
63 162
95 197
Well...those numbers suck but it does prove that the UL is no longer stopping below 170 UL (my highest ever). Will test later, too.
I went outside and ran it a couple more times and it's looking good.
DL 474, 959 UL 322, 241
Thanks, installed fine for me. Upload is still ify.
Sent from my SPH-D700 using Tapatalk
It installed fine for me. Still doesn't seem to be working right.
Do i have to install all my stuff again to install this? And is this the real update?
First off this is my first android phone and this is one heckuva community ! Still hadn't gotten any OTA update so I installed with this one. Installed perfectly with clockworkmod, speedtested on two different servers and it seems to have fixed the problem! Sending that screenshot to my e-mail was also much less painful Thanks newkidd!
davidrules7778 said:
Do i have to install all my stuff again to install this? And is this the real update?
Click to expand...
Click to collapse
i guess i should have said, this is the OTA update. no changes have been made to it. ill let someone else which more adept skills do what they do best. I simply just got the notification, grabbed it from cache and threw it up here. just trying to do my part
davidrules7778 said:
Do i have to install all my stuff again to install this? And is this the real update?
Click to expand...
Click to collapse
Yeah ull need to have the stock apps and odex files or wait for someone to take this and make ita zip file we can just flash through clocworkmod. I tried it and it aborted after it didn't find some odex file ...
Sent from my SPH-D700 using XDA App
Does this effect root or cwm? I'm unrooted at the moment because i only use root to remove apps, which would have pointless because i wanted this.
Guys, please report battery life with this update in the next few days. I know DI07 greatly reduced it (due to that DRM service it seems), but I'm hoping this one is better.
spitefulrain said:
Does this effect root or cwm? I'm unrooted at the moment because i only use root to remove apps, which would have pointless because i wanted this.
Click to expand...
Click to collapse
My root was kept through the update. I was running on stock with just joey's root fix and it is still rooted after the update.
I haven't rebooted, but I suspect I may have to reinstall recovery, though, because when I looked in the update.zip, they had the recovery-install in there again. Not confirmed, though.
The update came in OTA for me about 10 minutes ago. I went ahead and applied it, and with about 5-10% left on the status bar at the bottom (during the Updating modem phase) it seems to have hung. Most of the 10 minutes has been stuck in that spot. I'm afraid to pull the battery and brick it, but on the flip side it's doing me no good if it's just sitting here like this permanently, either. Anyone else see anything similar?
And I am currently running completely stock and NOT rooted, so I should be the perfect target candidate for the update. Haven't had the time or need yet to make those changes.
Worked beautifully. Make sure you flash back to stock DI07. This will delete your clockwork recovery, but not your root script.
It works
Installed using stock recovery (i.e. signature verification works).
I used noobnl's zip dump of DI07 to restore files I had removed/replaced.
I applied this update without removing root and had root after updating. (Verified with titanium as well as terminal emulator by running commands $su, # remount rw /system) note that I had replaced the oneclick busybox with titanium's download to keep it happy.
Note: I had rooted at DI07 since I used ODIN at this point in the past, so I was using a newer version of the one-click root.
3G speed test results:
Ping (ms)/Down (kbps)/Up (kbps)/Location
207/261/541/At my cubicle (top floor, but 500ft away from the nearest exterior wall/window)
325/307/547/In a breezeway (also top floor, exterior windows on both sides)
EDIT:
172/675/699/Courtyard ~100 feet from nearest building under a tree.
Still looking like upload is faster than download in my area... but it's definitely fixed.
Also: here's my tethered results (from my cube)
It doesn't affect root - I was rooted before and I still am. First thing I did once the update installed was remove junk apps after having to put them back for the update to work.
Recovery seems to be gone, though. I installed it through clockwork but I just tried booting into recovery again and it brought me to the stock recovery. So it seems you'll have to reinstall clockwork if you apply the update.
Speed test results are atrocious, but that's the norm in the middle of the day near my office. This morning I had 725/146, but I've run three tests since then, all AFTER applying the DI18 update:
82/10
283/16
221/29
Yes, 82/10. You read that right. That is what 3G is like where I am sitting right now. But I have 4G here so it doesn't matter. And 3G seems to be a little better in other places. I will test again in a different area and see if this improves uploads.
I take it from all of these positive responses that nobody else experienced it hanging near the end of the flash process?
Anyone with experience have any recommendations on what I do?
I just tried to flash this using clockwork, didn't like that I have the Galaxy MobileAP installed and not the Sprint one and aborted. Will have to wait until somebody else releases a version that will work anyways.
TurboFool said:
I take it from all of these positive responses that nobody else experienced it hanging near the end of the flash process?
Anyone with experience have any recommendations on what I do?
Click to expand...
Click to collapse
Pull the battery and flash to stock using odin would be one option.
FrumRoll said:
I just tried to flash this using clockwork, didn't like that I have the Galaxy MobileAP installed and not the Sprint one and aborted. Will have to wait until somebody else releases a version that will work anyways.
Click to expand...
Click to collapse
EDIT: see Firon's post on page 6 (#53) it will restore any modifications you've made (including MobileAP) as long as you have a stock (odexed) DI07 ROM, it won't even mess up recovery or kernel!
FrumRoll said:
Pull the battery and flash to stock using odin would be one option.
Click to expand...
Click to collapse
Unfortunately I'm nowhere I can do that right now. Also, won't that kill my data?
Hi, all. I just installed webOS 3.0.4 and now I can no longer get to the Moboot bootloader for booting into CM7. I (perhaps foolishly) did the update via HP's official Update Manager instead of by Preware. Just posting here to give you guys a heads up if anyone else is running Android and is thinking about updating to 3.0.4.
This should be an easy fix, I'm going to just try and reinstall Moboot via novacom. I'm guessing Android is still there, but the HP update just changed the boot back to stock.
EDIT: Yup, reinstalling Moboot fixed the problem.
Similar issue
I have a similar issue, once I updated to 3.04, reinstalled moboot and CM7 now it just hangs at the CM7 loading screen and does nothing. I've downloaded all teh files 4 times, reinstalled after wiping everything clean, still not working.
Don't know if this will help resolve why. I just loaded moboot and cm7 on my 3.0.4 touchpad and it works great. Maybe you need to recover the webos original form, update tp 3.0.4, them do the dual boot. Dunno
edit oops, just saw the first post edit. LOL
You should always CMW backup before doing any updates.
3 0 4 Update Breaks Moboot
You need to run it after the first update, i think the update that breaks it is called librsvg or something similar. I had it aswell on a new install of Sabayon 7 gnome, but running the command mentioned above fixed it straight away.
Hi Guys,
Having a bit of a nightmare here.
A few months back I installed CM9 on my HTC Sensation, everything went well, chuffed to bits with its performance and stability.
However, there was one small gripe that I just couldn't fix. The Youtube application doesn't work properly. If I'm on Wi-Fi then it works as desired but when I'm not at home I have major issues.
It will let me login and pulls down my subscribed channels etc etc but then as soon as I try to watch a video I get the error message:
"Connection to server lost
Touch to retry"
I have full signal/HSDPA and it just will not work. So far I've tried:
- Cleared the app data / cache
- Un-installed Youtube and re-downloaded it from the Play Store
- Reverted to an older version of Gapps.
- Flashed my ROM to the nightly CM9 build, still nothing.
It worked fine before my previous upgrade to CM9. The Youtube mobile site works, but it's crap. It's driving me insane! Please help!
Thanks!
I found the same issue that somebody is having on their Samsung Galaxy SII:
http://forum.xda-developers.com/showthread.php?p=28319322#post28319322
It appears that they managed to fix theirs, but none of the fixes mentioned in that thread work for me. Still getting exactly the same error.
I'm guessing that nobody has had this issue before?
After trying ABSOLUTELY everything I have finally resolved the issue.
Thought I would post incase anybody else finds this thread on Google!
You need to revert back to an old version of Gapps, I tried the March 12 release but had the same problems. I reverted back to the Feb 12 release and it worked! Youtube has updated to the latest version and is now working.
I found the Feb 12 release on http://goo.im/gapps , a link to the file is:
http://goo.im/gapps/gapps-ics-20120212-signed.zip
Install the zip with CWM and it now works!!! :good:
jaffster said:
After trying ABSOLUTELY everything I have finally resolved the issue.
Thought I would post incase anybody else finds this thread on Google!
You need to revert back to an old version of Gapps, I tried the March 12 release but had the same problems. I reverted back to the Feb 12 release and it worked! Youtube has updated to the latest version and is now working.
I found the Feb 12 release on http://goo.im/gapps , a link to the file is:
http://goo.im/gapps/gapps-ics-20120212-signed.zip
Install the zip with CWM and it now works!!! :good:
Click to expand...
Click to collapse
Thanks. That solved my issue but why the quality now is just terrible on HD. HD looks just like my webcam in the black hole. :/
NOOB HERE!!!
My quick and hopefully simple question regards installing the CM updates that are available directly on my phone. I am running 10.2 with no issues. Nearly everyday I get the icon stating there is an up to CM10. I simply click on it and install. Again, so far so good but I would like to know if simply installing these updates this way is "endangering" my phone. Is there a better way I should be installing these? I am assuming not otherwise the updates would not be present and as simple to install. Thanks for your input!
kcoop99 said:
NOOB HERE!!!
My quick and hopefully simple question regards installing the CM updates that are available directly on my phone. I am running 10.2 with no issues. Nearly everyday I get the icon stating there is an up to CM10. I simply click on it and install. Again, so far so good but I would like to know if simply installing these updates this way is "endangering" my phone. Is there a better way I should be installing these? I am assuming not otherwise the updates would not be present and as simple to install. Thanks for your input!
Click to expand...
Click to collapse
It is perfectly safe to use the built in cmupdater every day. For piece of mind it may be a good idea to occasionally make a backup manually using your recovery of choice (either TWRP or CWM).
If you ever encounter a problem after upgrading to the latest nightly, and nightlies do sometimes break features, just boot into recovery and manually flash the previous day's file (located in the /cmupdater folder)...no need to wipe anything.
I've been dirty flashing cm nightlies since June. You're fine. A clean flash doesn't hurt once in awhile though!
Thanks! I appreciate it!
I dirty flashed for a year with no problem at all untill a few days ago. I went from the 8/16 to the 8/17 to the 8/14 and lost my imei and eri once the 8/14 booted. Ive been trying everything with no luck to get the eri back. make sure you do a full (not just imei) NV back up and do a normal rom/data backup like once ever week or two. Im regretting not doing a NV backup as the only tool to fix my problem has been removed from the site due to infringing the ToS.
Hey guys,
So here is a straight from source build of Android L, 5.0. I have not done anything beside build it from source and flash it. I have not done extensive testing on it.
So anyways, here is the link:
http://d-h.st/zi0
I have not included gapps or anything else. They will be coming soon. This build is primarily to play around with. I would not consider this a daily driver.
Issues:
Probably a ton, seeing as I have only checked if it boots.
I am not responsible for any issues this may cause or anything else that may happen to your tablet as a result of this.
I also have a ton of schoolwork and other things that keep popping up, so my support may be iffy. Please bear with me or go back to 4.4.4.
Here is a screenshot for proof:
https://www.dropbox.com/s/lnmhdapeemskggi/1743495_10153594576754572_4551962379003400239_n.jpg?dl=0
Future Plans for this Rom:
GApps are not yet possible on Lollipop as far as I can work out, due to the fact that baksmali and smali do not appear to play nicely with ART odex files. I will be rebuild the rom to be odexed and then including a gapps package.
XDA:DevDB Information
[Android 5.0] Straight from source ROM, ROM for the Nexus 7
Contributors
MidnightNinja
Version Information
Status: Testing
Created 2014-11-05
Last Updated 2014-11-04
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
cchant said:
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm..let me know if you still have issues, because I was able to sideload on my device
Awesome!!
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Niekhout02 said:
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Click to expand...
Click to collapse
I am missing alot of the google stuff, which is probably why none of that works
That will come shortly, I just need to redo a lot of my vendor files and such to get gapps to be built in.
It worked even though it said no OS
first boot takes awhile but it works!
Confirmed it works.
Sideloading gapps for cyanogenmod 11 and hoping they auto update does not work. Worth a shot though. Time to reflash.
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Working great! I think performance is even better than kitkat
Wi-Fi also working (maybe bluetooth, nfc and gps too)
StardustGeass said:
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Click to expand...
Click to collapse
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
tatazeuz said:
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
Click to expand...
Click to collapse
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
MidnightNinja said:
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
Click to expand...
Click to collapse
Yay!
Works great, now waiting for gapps
thanks
Gapps mostly work fine if you edit updater.script
I've only had issue with the keyboard crashing so I'd suggest removing it from the gapps package before flashing.
Woah
I can't wait for the final version, this one, using 4.4.4 binaries, is crazy smooth. Google outdid theirselves on the optimization department.
Awesome work, think im gonna givebthis a try atbwork tomorrow.
What does work and what doesn't
basuraunak said:
What does work and what doesn't
Click to expand...
Click to collapse
So far, everything seems to be working. Have to check camera yet though.
I cant seem to get much else to go with it, but I will share my findings.
I can get TWRP to install,but then I get a bootloop.
If you use the Nexus Root Toolkit v 1.9.3 and "Root" with custom recovery checked. It freezes after trying to temporarily boot the modified boot image.
Hard reset the tablet and boot normally. The toolkit should reboot your tablet back into the bootloader and into TWRP, but this is only good for one boot.
If you mount /system and run a fix permissions, then it stays installed, but never gets past the boot screen.
It boots far enough to get into ADB.
Not sure what to try next though...
I was thinking if we could get a flashable zip without the stock recovery, then we may be able to keep TWRP, but I am not familiarwith building the flashable zips.
Wait, So how do you flash the google play services after you lose TWRP?! I don't understand..