Related
seems this is not the latest ota? regardless is a pretty good rom up to you =).
Changelog:
v1.0.a
removed libui.so with tp wake, made the rom bootloop
Features
Rooted
Deodexed
Zip Aligned
Busybox included
Rom Manager
Dsp Manager
Wifi Calling(Tmobile include's this by default)
ScreenShots
Download Link
http://android-maisters.ddns.net/downloads/Vision-Aosp-Stock/Vision-Aosp-Stock-v1.0.zip
Click to expand...
Click to collapse
Patch to fix boot loops
http://android-maisters.ddns.net/downloads/Vision-Aosp-Stock/Vision-Aosp-tock-v1.0.a-patch.zip
Thanks to:
Cyanogenmod for dsp manager app/libs
rodraf for posting ota in tmobiel forums.
This looks fun =] Thanks Siulmagic
And this is different than virtous g lite? Were not even sure this is the official ota version yet I thought. Reports were that officia ota is 2.15.xxx.3 Thanks for the effort regardless of what the outcome is, ur roms are always nice!
Sent from my HTC Vision using XDA Premium App
Double post
xsteven77x said:
And this is different than virtous g lite? Were not even sure this is the official ota version yet I thought.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
not sure dunno what virtuos g lite is using as base. and yes this is the official update.
omggggg, i was gunna make this.
great work siul!! amazing as always =) better than i would have done anyway
interesting release...
this isn't based on the official ota, though?
Build: 2.15.531.3 <-- that is the official release build. this is 2.13.
maybe I'm wrong?
i guess no dutch language but i will try it hope it is better as cyan cheers
pmcqueen said:
interesting release...
this isn't based on the official ota, though?
Build: 2.15.531.3 <-- that is the official release build. this is 2.13.
maybe I'm wrong?
Click to expand...
Click to collapse
that's what the guy in forum said, and that's the version in the build.prop, blame tmobile =P
Tried installing this through recovery. First time over the leaked t-mobile GB without any wipes and it just boot looped. So went back to recovery. Wiped everything. Did a clean install of this zip. I still just get boot loop. Having to do a restore.
mike102871 said:
Tried installing this through recovery. First time over the leaked t-mobile GB without any wipes and it just boot looped. So went back to recovery. Wiped everything. Did a clean install of this zip. I still just get boot loop. Having to do a restore.
Click to expand...
Click to collapse
same here v_v
SmartBrother90 said:
same here v_v
Click to expand...
Click to collapse
Wrought Ro Scooby.
mike102871 said:
Tried installing this through recovery. First time over the leaked t-mobile GB without any wipes and it just boot looped. So went back to recovery. Wiped everything. Did a clean install of this zip. I still just get boot loop. Having to do a restore.
Click to expand...
Click to collapse
Same here. I wiped and installed three times, but still got a boot loop.
let me flash the rom see whats wrong.
i know whats wrong guys its a quick fix, you guys whant a flashable patch? or the whole rom?
siulmagic said:
i know whats wrong guys its a quick fix, you guys whant a flashable patch? Or the whole rom?
Click to expand...
Click to collapse
patchhhhhh!!!!
SmartBrother90 said:
patchhhhhh!!!!
Click to expand...
Click to collapse
whatever works, not too picky as we havent really been able to boot it, its not a big deal to flash a new version
siulmagic said:
that's what the guy in forum said, and that's the version in the build.prop, blame tmobile =P
Click to expand...
Click to collapse
(EDIT for further clarification: Check the PC10IMG.zip from May's size and that leaked build's size that was posted on the T-Mo community. Same size, down to the byte.)
This is incorrect information, and the wrong build altogether. The 2.13.531.8 build is what is in that post on the new T-Mobile community. That is the last leaked build from May, which was put on handsets mistakenly that were sent out as refurbs. 2.15.531.3, yesterday's build, is going to most likely be a "patch" style of update.zip, which will have the differences to be applied to the current software on the phone, thereby making it a smaller sized update, but won't have the complete set of files for the OS. So in tthe end, there is not yet a solid structure to build a nnew ROM on top of. No offense, siulmagic, but this is the same as the last one. Dig through more of the files and you will see exact matches. From what I saw, the newest build has the updated Google Music icon from the new Google Music Beta enabled app. Also, I believe the new Market is built in. Your images above, show the old Google Music icon. Either way, the build that was posted in the forums was just a re-post of the leaked build from May, since the T-Mobile forums were completely re-done, and some people there know nothing about visiting the XDA forums.
flamingblue8z said:
This is incorrect information, and the wrong build altogether. The 2.13.531.8 build is what is in that post on the new T-Mobile community. That is the last leaked build from May, which was put on handsets mistakenly that were sent out as refurbs. 2.15.531.3, yesterday's build, is going to most likely be a "patch" style of update.zip, which will have the differences to be applied to the current software on the phone, thereby making it a smaller sized update, but won't have the complete set of files for the OS. So in tthe end, there is not yet a solid structure to build a nnew ROM on top of. No offense, siulmagic, but this is the same as the last one. Dig through more of the files and you will see exact matches. From what I saw, the newest build has the updated Google Music icon from the new Google Music Beta enabled app. Also, I believe the new Market is built in. Your images above, show the old Google Music icon. Either way, the build that was posted in the forums was just a re-post of the leaked build from May, since the T-Mobile forums were completely re-done, and some people there know nothing about visiting the XDA forums.
Click to expand...
Click to collapse
iv already removed anything stating its an ota in op, i made a mistake , it happens to the best of us, regardless its a pretty good and fast rom, so iv decided to leave it.
siulmagic said:
i know whats wrong guys its a quick fix, you guys whant a flashable patch? or the whole rom?
Click to expand...
Click to collapse
Doesn't matter here! Just wanna get this ROM booted and see what it's got.
If there's already source for 4.0.3 why don't devs (whom i'll always not thanks enough for their work) makes an update? Only Google can make an incremental update and we need a full AOSP rom ?
? There are 4.0.3 roms
all the main roms i see in the dev section are 4.0.3
Sorry if i wasn't clear enough.
I mean: i'm on stock 4.0.1 and i don't want to wipe now. Isn't there a way to make an incremental update 4.0.3 instead of flashing an entire rom?
Also as a Nexus device, wasn't one of the benefits that Google would put out the updates very quickly?
They have 4.0.3 just sitting there, is there any reason why they're not putting it out?
The 4.0.3 roms are based off from the uncompiled 4.0.3 source that google releases to the public, which developers can compile and test their apps on.
As for your 4.0.1, is your device a yakju, or jakjuux? Check with the GN checker app on the market. If its jakjuux, it wont be updated until samsung says so, meanwhile if you are running jakju, you should be able to go to 4.0.2, which has been released as an OTA through google. Hope this helps.
Sent from my MZ604 using xda premium
F0l3ert said:
The 4.0.3 roms are based off from the uncompiled 4.0.3 source that google releases to the public, which developers can compile and test their apps on.
As for your 4.0.1, is your device a yakju, or jakjuux? Check with the GN checker app on the market. If its jakjuux, it wont be updated until samsung says so, meanwhile if you are running jakju, you should be able to go to 4.0.2, which has been released as an OTA through google. Hope this helps.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
I'm yakju bu you didn't get my point or neither i'm not explaining what it could be only my imagination. BUT
If the source code it's released why it can't be a 6/10/20 mb packet that can upgrade my system like a FOTA update can do ?
Because 4.0.3 has some bugs that needs to be fixed. The 4.0.3 OTA was released for Nexus S then pulled because of the bugs it was having.
You think if it was ready, they'd release it. Give it time, people are so ungrateful when 95% of the Android Community are still on Android 2.3.X and below.
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
zephiK said:
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
Click to expand...
Click to collapse
I've never complained and you didn't answered my question
zephiK said:
Because 4.0.3 has some bugs that needs to be fixed. The 4.0.3 OTA was released for Nexus S then pulled because of the bugs it was having.
You think if it was ready, they'd release it. Give it time, people are so ungrateful when 95% of the Android Community are still on Android 2.3.X and below.
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
Click to expand...
Click to collapse
Not really, there's a source released for the GNex from Google.
Sugar0, I will try compiling that stock source and tell you how it goes.
Arrio said:
Not really, there's a source released for the GNex from Google.
Sugar0, I will try compiling that stock source and tell you how it goes.
Click to expand...
Click to collapse
You don't need to! It's plenty of stock untouched AOSP roms and modified.
What i'm asking is:
is there an unofficial small update that will bring 4.0.3 to my GN that i can flash in recovery ? Not the full rom!
sugar0 said:
You don't need to! It's plenty of stock untouched AOSP roms and modified.
What i'm asking is:
is there an unofficial small update that will bring 4.0.3 to my GN that i can flash in recovery ? Not the full rom!
Click to expand...
Click to collapse
Oh then no.. not at the moment.
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Finally an on-topic answer! Why aren't those updates around ? Do i miss something ?
No, you didn't "miss" anything. It's just that most people who are going to take the time to setup a build environment are doing so to tinker with the source -- not just build a vanilla package. Either way, its not terribly difficult to setup and build -- especially with all the guides floating around XDA.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
That's not strictly true. The 'OTA' package you make when compiling the ROM from source is still a complete ROM as opposed to a small OTA update
It won't require a system wipe and will apply just like an OTA, which is what (I'm assuming) the OP wanted.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
It won't require a system wipe and will apply just like an OTA, which is what (I'm assuming) the OP wanted.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yep! like nigthly build of Cyanogenmod. It doesen't matter if its 6mb or 120mb. So aren't there those updates around ? I can't understand why they don't make such updates
I just updated my Chrome from the market place, and now when I try to start it I get the message:
Chrome is not supported for your version of Android.
Version 4.0 (Ice Cream Sandwich is the minimal supported version.
Click to expand...
Click to collapse
I'm running CyanogenMod9, Android version 4.0.3 so it should work....
Any ideas?
Same symptom and likely same cause as this.
It doesn't work for me either
Damnit can anyone upload the original, or maybe a build prop tweak so we can use this? I cannot go back to any other browser after using this. I'm sure more people feel the same way
Edit: 1000th post. Awesome haha
Sent from my CM9 Epic 4G
jeremysv said:
Same symptom and likely same cause as this.
Click to expand...
Click to collapse
i running cm9 with the version you quoted it works still. maybe you did something to break it.
checking the market. there is an update its 0.16.4215.215, in my market it is. not 0.16.4130.199 which the one i have. used titanium backup to get the old one.
xopher.hunter said:
Damnit can anyone upload the original, or maybe a build prop tweak so we can use this? I cannot go back to any other browser after using this. I'm sure more people feel the same way
Sent from my CM9 Epic 4G
Click to expand...
Click to collapse
Old version courtesy of I Brick Phones
I Brick Phones said:
for those who accidentally updated Chrome i've uploaded the previous version http://db.tt/4onutkFj
Click to expand...
Click to collapse
Sent from my CM9 Epic 4G
You can find the original apk Here
Reinstall it over the updated one and you'll be good to go. Im sure the CM9 devs will figure this out quickly or Google might release a patch if the want to be friendly to us geeks.
xopher.hunter said:
Damnit can anyone upload the original, or maybe a build prop tweak so we can use this? I cannot go back to any other browser after using this. I'm sure more people feel the same way
Sent from my CM9 Epic 4G
Click to expand...
Click to collapse
i made these changes to build.prop. got from stock galaxy nexus. dont know if all need to be changed but it is what i did and new version is working. just find these lines and change to these.
ro.build.id=IMM30B
ro.build.display.id=IMM30B
ro.build.version.release=4.0.4
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.build.description=SPH-D700-user 4.0.4 IMM30B release-keys
ro.build.fingerprint=sprint/SPH-D700/SPH-D700:4.0.4/IMM30B/EI22:user/release-keys
s89281b said:
i made these changes to build.prop. got from stock galaxy nexus. dont know if all need to be changed but it is what i did and new version is working. just find these lines and change to these.
ro.build.id=IMM30B
ro.build.display.id=IMM30B
ro.build.version.release=4.0.4
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.build.description=SPH-D700-user 4.0.4 IMM30B release-keys
ro.build.fingerprint=sprint/SPH-D700/SPH-D700:4.0.4/IMM30B/EI22:user/release-keys
Click to expand...
Click to collapse
Worked like a charm thank you very much. Took all but 2 minutes to do with an app I found on the market and ICS's awesome copy and paste/multitasking enhancements.
Sent from my CM9 Epic 4G
s89281b said:
i made these changes to build.prop. got from stock galaxy nexus. dont know if all need to be changed but it is what i did and new version is working. just find these lines and change to these.
ro.build.id=IMM30B
ro.build.display.id=IMM30B
ro.build.version.release=4.0.4
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.build.description=SPH-D700-user 4.0.4 IMM30B release-keys
ro.build.fingerprint=sprint/SPH-D700/SPH-D700:4.0.4/IMM30B/EI22:user/release-keys
Click to expand...
Click to collapse
It turns out the only change necessary to make Chrome work is ro.build.id. I wrote a detailed analysis of this issue in this blog entry. Be sure to read the warning!
wtogami said:
It turns out the only change necessary to make Chrome work is ro.build.id. I wrote a detailed analysis of this issue in this blog entry. Be sure to read the warning!
Click to expand...
Click to collapse
yeah i figured it was only one line but i found gingerbread mentioned several times and i wanted to get rid of all mention of it. and i was to lazy to test one line at a time. thanks for clearing that up.
Chrome app working again
All you have to do is backup your data and reflash cm9 and gapps and reinstall the downloaded apk , the market may give you some problems .
Update to alpha 5... they fixed chrome beta update issue... otherwise find older versions of apps on applanet.net
Sent from my SPH-D700 using xda premium
Which versions of a custom rom of ICS 4.0 support Google Chrome?
---------- Post added at 11:44 AM ---------- Previous post was at 10:58 AM ----------
The reason I ask is because there are so many ICS themed roms, what constitutes one that'll work vs won't?
KC_RSX said:
Which versions of a custom rom of ICS 4.0 support Google Chrome?
---------- Post added at 11:44 AM ---------- Previous post was at 10:58 AM ----------
The reason I ask is because there are so many ICS themed roms, what constitutes one that'll work vs won't?
Click to expand...
Click to collapse
you would need to be using CM9, Alpha 5 if you wanted the latest update to work out of the box. To get CM9 Alpa 5 go here: http://epiccm.blogspot.com/p/cm9-install-guide.html
So ANY ROM using CM 9 and Alpha 5 will work? Not familiar with what Alpha 5 is, what's that? (had someone root me n do my flashing of roms.. Still pretty new to it)
THX
Sent from my SPH-D710 using XDA App
KC_RSX said:
So ANY ROM using CM 9 and Alpha 5 will work? Not familiar with what Alpha 5 is, what's that? (had someone root me n do my flashing of roms.. Still pretty new to it)
THX
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Are you using the Epic 4G (non-touch)? If so there is only one cm9 alpha 5. It is it's own ROM.
Sent from my SPH-D700 using Tapatalk
When we'll have cyanogenmod 10.1 (Android 4.2) on us devices?
Thanks
3 days after the yesterday of the day before it
Sent from my Jellybean Xperia S
Ben36 said:
3 days after the yesterday of the day before it
Sent from my Jellybean Xperia S
Click to expand...
Click to collapse
So tomorrow? xD
Ben36 said:
3 days after the yesterday of the day before it
Sent from my Jellybean Xperia S
Click to expand...
Click to collapse
Creative, I like it. I was thinking something along the lines of before Cyanogenmod 11 and after Cyanogenmod 10
4lex96 said:
When we'll have cyanogenmod 10.1 (Android 4.2) on us devices?
Thanks
Click to expand...
Click to collapse
5 days to go...
Sent from my IPhone 6 using Android 5.0
ap030993 said:
5 days to go...
Sent from my IPhone 6 using Android 5.0
Click to expand...
Click to collapse
I think that Kali- has just managed to get the Xperia T booting 4.2 not sure about the S
fareeed said:
I think that Kali- has just managed to get the Xperia T booting 4.2 not sure about the S
Click to expand...
Click to collapse
I have no information on that...but free xperia website says 5 days to go for release and the change log has also been updated with CM 10.1 - Latest CM 10.1
Sent from my IPhone 6 using Android 5.0
ap030993 said:
I have no information on that...but free xperia website says 5 days to go for release and the change log has also been updated with CM 10.1 - Latest CM 10.1
Sent from my IPhone 6 using Android 5.0
Click to expand...
Click to collapse
It says WIP, not necessary release.
Felimenta97 said:
It says WIP, not necessary release.
Click to expand...
Click to collapse
That's true, I'm just basing what I said on seeing Kali- post a picture of it up and running on the T on Google+ and all the mr1-staging patches on gerrit seem to be either specifically for the mint or blue-common. But yeah like you say it's a WIP so no release dates yet
fareeed said:
That's true, I'm just basing what I said on seeing Kali- post a picture of it up and running on the T on Google+ and all the mr1-staging patches on gerrit seem to be either specifically for the mint or blue-common. But yeah like you say it's a WIP so no release dates yet
Click to expand...
Click to collapse
Yea i know it's a WIP and it's just to indicate that it is not fully working ,before they just made a section in the website but this week they have added it to the change log . There's a possibility that they might release a beta version and then update it weekly.
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
klobkelosh said:
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
Click to expand...
Click to collapse
I'm on a Windows machine and came across those on Google's site. I used a text editor to open the shell script and then deleted all lines above the binary data, then saved, then renamed the file with a .tar.gz extension. I could then open that and see all of the files. Try that.
Turns out I had a space on the file path! Thanks mmuzzy for pointing that out...
If anyone wants the TORO binaries as a flashable zip, here: http://d-h.st/fpN
Tested on cm 10.1 latest nightly. All ok. Even fixes a gps issue with cm.
Tiny did a few more tweaks. His version fixes the gps wakelock issue:
New link: URL=http://d-h.st/Lgo]422-JDQ39-toro-proprietaries.zip - 4.45 MB[/URL]
Tiny Pulled the file that caused dev-host to complain about a virus (fRom) that I originally included. Tiny can't find anything about this file so it's a false positive but to be sure, he uploaded a new zip and removed the old one
Thanks tiny!
Link fix
http://d-h.st/Lgo
Sent from my Galaxy Nexus using xda app-developers app
Maguro JB 4.2.2 JDQ39 Binaries
Hi guys!
Here's the Maguro JB 4.2.2 JDQ39 Binaries :good:
http://forum.xda-developers.com/showpost.php?p=38650434&postcount=2641
klobkelosh said:
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
Click to expand...
Click to collapse
I didn't know you were over here now :good:
CondemnedSoul said:
I didn't know you were over here now :good:
Click to expand...
Click to collapse
Hey hey cs! How you doing man?
Yeah, I've been over here since vzw gnex release day. You still deving?
klobkelosh said:
Hey hey cs! How you doing man?
Yeah, I've been over here since vzw gnex release day. You still deving?
Click to expand...
Click to collapse
Sweet.... I'm doing pretty good. Finally getting things in order with life. Yes, still deving.... just received a gnex yesterday. Checking things out over here and waiting on a sim card. Should have it Monday I think.
CondemnedSoul said:
Sweet.... I'm doing pretty good. Finally getting things in order with life. Yes, still deving.... just received a gnex yesterday. Checking things out over here and waiting on a sim card. Should have it Monday I think.
Click to expand...
Click to collapse
cool! Hoping you build for Toro!
I haven't pulled off my own ROM yet, but I've done a bunch of porting, theming, and tinkering, mostly for myself. See ya round!
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
kamil.trebunia said:
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
Click to expand...
Click to collapse
The binaries in this thread are for toro only. I wouldn't advise flashing them on maguro. There is a link to proper Gsm binaries a few posts back that can be flashed.
Sent from my Galaxy Nexus using Tapatalk 2
Nice.
Sent from my Paranoid Nexus 3.0
klobkelosh said:
cool! Hoping you build for Toro!
I haven't pulled off my own ROM yet, but I've done a bunch of porting, theming, and tinkering, mostly for myself. See ya round!
Click to expand...
Click to collapse
You should post them ... Don't be greedy! .... I will be soon
Sent from my ADR6400L using Tapatalk 2
kamil.trebunia said:
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
Click to expand...
Click to collapse
Any factory image for the same android build will have the same binaries (and probably others that can't be distributed as open source) as the ones posted for aosp.
I pulled the GPS, Wi-Fi, and Bluetooth drivers from mwalt2's deodex of last night's ota leak: VZW_JDQ39_GPS+WIFI_DRIVERS.zip - 1.22 MB. Not sure if they are any different than the AOSP binaries, but here they are if you want them. Phone is deep sleeping like a baby, GPS locks right on, and Wi-Fi seems good.
klobkelosh said:
I pulled the GPS, Wi-Fi, and Bluetooth drivers from mwalt2's deodex of last night's ota leak: VZW_JDQ39_GPS+WIFI_DRIVERS.zip - 1.22 MB. Not sure if they are any different than the AOSP binaries, but here they are if you want them. Phone is deep sleeping like a baby, GPS locks right on, and Wi-Fi seems good.
Click to expand...
Click to collapse
Flashing these over Mmuzzy's 3/2 Vanilla build is ok?
n99hockey said:
Flashing these over Mmuzzy's 3/2 Vanilla build is ok?
Click to expand...
Click to collapse
Yes, should work fine.
Can these be flashed on a 4.1.2 ROM and get improvement?
Galaxy Nexus+Baked+Lean+TWRP=BOOM SHAKALAKA
TMFGO45 said:
Can these be flashed on a 4.1.2 ROM and get improvement?
Galaxy Nexus+Baked+Lean+TWRP=BOOM SHAKALAKA
Click to expand...
Click to collapse
Let us know after you flash it!