Develop Bugs

any chance for NAND?

How for is the development for NAND for the Touch pro ? (thinking of buying one tomorrow)

Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.

robuser007 said:
How for is the development for NAND for the Touch pro ? (thinking of buying one tomorrow)
Click to expand...
Click to collapse
why would you buy a touch pro when the tilt2/touch pro 2 is already out ?

gmanfuzing said:
why would you buy a touch pro when the tilt2/touch pro 2 is already out ?
Click to expand...
Click to collapse
Becuase I found one on ebay for $45.

babijoee said:
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
Click to expand...
Click to collapse
If they're looking for testers I'm game. I'm no stranger to all that stuff coming from Vogue.

mrkite38 said:
Becuase I found one on ebay for $45.
Click to expand...
Click to collapse
hmm 45 dollars isn't bad then. Still i wish the tilt 2 was out when i got mine. its what the phone should've been like in the first place seeing as the processor isn't even better.

All nonsense aside, whats the status of nand support?

the0ne.john said:
All nonsense aside, whats the status of nand support?
Click to expand...
Click to collapse
See post #2.

babijoee said:
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
Click to expand...
Click to collapse
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!

arrrghhh said:
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
Click to expand...
Click to collapse
Agreed - the only things I 'expect' to work reliably before flashing to nand are calls and data. Everything after that is gravy.
And bt audio works on cupcake and donut for vogue, but not on eclair. And the vogue's camera is just crap, regardless of os.

arrrghhh said:
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much ) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
Click to expand...
Click to collapse
I agree. I've been a full time Android user for the last two and a half months . No complaints here.

any news?¿ will be an android rom some day? or we shouldn´t expect that

There is NAND launcher/support for HTC Kaiser. Is it that hard to port over build one for toouch pro?

volcan123 said:
There is NAND launcher/support for HTC Kaiser. Is it that hard to port over build one for toouch pro?
Click to expand...
Click to collapse
where can i found that?¿
thanks
EDIT: i have found this info:
http://forum.xda-developers.com/showthread.php?t=636024
http://forum.xda-developers.com/showthread.php?t=651861

we can learn from Vogue,it has opened source. http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi

Guys, believe me, WHEN the team wants to make it a ROM for NAND they will do it easily.
So just wait.

up！
I agree. I've been a full time Android user
hope the ROM for NAND，flash it

rayman18 said:
where can i found that?¿
thanks
EDIT: i have found this info:
Click to expand...
Click to collapse
Yup, thats what I am talking about. I wonder if the chefs for XDANDROID know about this?

rayman18 said:
where can i found that?¿
thanks
EDIT: i have found this info:
http://forum.xda-developers.com/showthread.php?t=636024
http://forum.xda-developers.com/showthread.php?t=651861
Click to expand...
Click to collapse
These threads are about how USERS can put an NAND build on their phone..
Okay I'm going to tell you guys this just once.
First the developers have to get everything finished so that we don't need the few bits from WinMo we still do.
Then they can make a NAND build.
And BELIEVE me, they know how to do it. It just won't work at the current state of things.
And the XDAndroid team knows just as much about porting as the Vogue guys. The only difference is that we got more advanced phones and therefor it takes a LOT more time to make a port.

x2 right now the biggest thing is drivers. since there were never any drivers made for the touch pro/fuze for android, none exist.
since none exist, we must use winmo to initalize alot of the hardware that android uses.
once the drivers are sorted out (they are being worked on) and we don't need winmo to initalize everything for android, android can be moved to nand.

[Q] What am I to do...

Ok, I am currently on contract with sprint until the end of next august. I was disappointed with the extended delay/final build of Froyo for this thing, and still trying to play the usuall waiting game on Gingerbread right now. My Epic i currently still "pure" and not rooted. I really don't want to risk Rooting it, but at this point I feel I should. I've been researching this for a while now but all I could come up with were very old articles,build roms, belated possible dates & info on the epic touch. Only thing I could get out of contacting sprint some time ago was the usuall "it's coming soon" I'm not the patient type.
So...you think I should quit my risk full induced hesitancy and root my phone then and there, or simply be stuck with froyo and keep playing the waiting game (If they don't decide to abandon releasing the build in favor of sticking with the new 4.0 /GSII lines).

I've got to say that for me the upgrade from Eclair to Froyo made a huge improvement in my Epic. I've rooted the phone so I can run various backup and and adblocker apps, but every time I try custom Froyo ROMS I end up going back to stock because of some odd problem or crash or something that doesn't work.
Right now I'm trying the Gingerbread EH17 leak with the source code compiled kernel, which is the most stable Gingerbread I've found. Is it better than Froyo? Yeah. Is it a lot better? nope. On a scale of 1 to 10,the upgrade from Eclair to Froyo went from 5 to 8, the upgrade to Gingebread takes it to 9. Graphics are a bit smoother, there are a few more options on some apps, Video calling is supported. Nothing to get too antsy about.
By the way, rooting Froyo is easy using the one-click method. Rooting Gingerbread requires using Odin right now, which makes it possible to brick the phone by checking the wrong options, although just reading the instructions carefully should make it pretty safe.

Jbluna said:
Ok, I am currently on contract with sprint until the end of next august. I was disappointed with the extended delay/final build of Froyo for this thing, and still trying to play the usuall waiting game on Gingerbread right now. My Epic i currently still "pure" and not rooted. I really don't want to risk Rooting it, but at this point I feel I should. I've been researching this for a while now but all I could come up with were very old articles,build roms, belated possible dates & info on the epic touch. Only thing I could get out of contacting sprint some time ago was the usuall "it's coming soon" I'm not the patient type.
So...you think I should quit my risk full induced hesitancy and root my phone then and there, or simply be stuck with froyo and keep playing the waiting game (If they don't decide to abandon releasing the build in favor of sticking with the new 4.0 /GSII lines).
Click to expand...
Click to collapse
If you waited this long, you might as well wait for the Gingerbread OTA...who knows maybe you'll be the first to get it! Wasn't Castro08 the first to get EC05 OTA? You'll be instantly famous
Sent from my Nexus S 4G using xda premium

Jbluna said:
Ok, I am currently on contract with sprint until the end of next august. I was disappointed with the extended delay/final build of Froyo for this thing, and still trying to play the usuall waiting game on Gingerbread right now. My Epic i currently still "pure" and not rooted. I really don't want to risk Rooting it, but at this point I feel I should. I've been researching this for a while now but all I could come up with were very old articles,build roms, belated possible dates & info on the epic touch. Only thing I could get out of contacting sprint some time ago was the usuall "it's coming soon" I'm not the patient type.
So...you think I should quit my risk full induced hesitancy and root my phone then and there, or simply be stuck with froyo and keep playing the waiting game (If they don't decide to abandon releasing the build in favor of sticking with the new 4.0 /GSII lines).
Click to expand...
Click to collapse
There is really no disadvantage to rooting your phone. There is a program called odin which you can return your phone back to 2.2 android. To root your phone all you have to do is copy a few files to your sd card and run a .bat or .sh (windows or linux) .
Rooting your phone puts you in control. You can remove programs that bug you or keep starting on there own. You could also put on a different rom. If you need more help let us know.

Wait it out. You're really not missing out on much. just a different version name and color scheme to be honest. So unless you got some girl at home waiting for you to wow her with a phone that's running GB. Take a number, sit back and worry about bigger things in life.
Sent from my CM7.1/*Apocalypse-Talon* v3.2.1 NS4G

.OmEgA said:
Wait it out. You're really not missing out on much. just a different version name and color scheme to be honest. So unless you got some girl at home waiting for you to wow her with a phone that's running GB. Take a number, sit back and worry about bigger things in life.
Sent from my CM7.1/*Apocalypse-Talon* v3.2.1 NS4G
Click to expand...
Click to collapse
+1, gingerbread is a little better than froyo, but nothing overly awesome about it. Cm7 (gingerbread) is pretty *****in, but u can do that from ec05...
Sent from my SPH-D700 using XDA App

Jbluna said:
Ok, I am currently on contract with sprint until the end of next august. I was disappointed with the extended delay/final build of Froyo for this thing, and still trying to play the usuall waiting game on Gingerbread right now. My Epic i currently still "pure" and not rooted. I really don't want to risk Rooting it, but at this point I feel I should. I've been researching this for a while now but all I could come up with were very old articles,build roms, belated possible dates & info on the epic touch. Only thing I could get out of contacting sprint some time ago was the usuall "it's coming soon" I'm not the patient type.
So...you think I should quit my risk full induced hesitancy and root my phone then and there, or simply be stuck with froyo and keep playing the waiting game (If they don't decide to abandon releasing the build in favor of sticking with the new 4.0 /GSII lines).
Click to expand...
Click to collapse
Ok first of all don't be afraid of rooting
2nd if you want out of your contract DO NOT TAKE NO for an answer from them! after the crap ass GPS on DI18 & more crap with EB13 & the camera not working right, I got out of my contract with sprint.
You just have to get past the "gate keeper" thats the first & some times the second person you get on the phone. All you have to do is start talking **** (with out cussing ) to them about the "crappy updates" & if they try & blame samsuck then you go into the fact that there NAME "SPRINT" is plastered on the fount of the dam phone & if there name is on something then they need to own up & take responsibility

Tmobile SGS3, no LTE, deal breaker?

So im ready to upgrade my phones on Tmobile and I read that the SGS 3 does not support LTE on Tmobiles network. Is this a deal breaker? Ive read that LTE is a battery vampire. Tmobile LTE network isnt due till next year. I plan on keeping the SGS 3 for 2 years, hoping it would be a bit of future proofing for me since its the hottest phone right now.
Is no LTE support a deal breaker?

Nope... I'm getting 10-15 down on a rough day in greater Los Angeles area. You really need it faster? Think it's good enough to perform every day activities on the phone.
Sent from my SGH-T999 using xda app-developers app

Yeah no way. I'm getting 20mps steady. That's stupid fast. Lte if available is quicker with better ping but the phone is excellent and Lte isn't needed with the new radios.
Sent from my SGH-T999 using xda premium

derek210 said:
Yeah no way. I'm getting 20mps steady. That's stupid fast. Lte if available is quicker with better ping but the phone is excellent and Lte isn't needed with the new radios.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Not only this but our device supports 41mbps, which by the time LTE rolls out, will be in most cities if not already.
(I know we wont get 41mbps realistically)
I already get 25mbps in NYC which is faster than my home internet speed. Seriously LTE is overkill (literally) as it just kills your battery.

androidmonkey said:
So im ready to upgrade my phones on Tmobile and I read that the SGS 3 does not support LTE on Tmobiles network. Is this a deal breaker? Ive read that LTE is a battery vampire. Tmobile LTE network isnt due till next year. I plan on keeping the SGS 3 for 2 years, hoping it would be a bit of future proofing for me since its the hottest phone right now.
Is no LTE support a deal breaker?
Click to expand...
Click to collapse
You should probably read before posting something that has been asked already.
The T999 has LTE bands already, they are just disabled by default.
Sent from my SGH-T999 using xda premium

I've looked at a billion comparisons...
androidmonkey said:
So im ready to upgrade my phones on Tmobile and I read that the SGS 3 does not support LTE on Tmobiles network. Is this a deal breaker? Ive read that LTE is a battery vampire. Tmobile LTE network isnt due till next year. I plan on keeping the SGS 3 for 2 years, hoping it would be a bit of future proofing for me since its the hottest phone right now.
Is no LTE support a deal breaker?
Click to expand...
Click to collapse
I'm no expert, but not much of a life living in a new state, so I read A LOT! And most of that reading has been about computers and mobile phones. I've seen about a million opinions on this; seen a lot of speed tests and other tests comparing the 2, and absolutely every piece of factual evidence so far has shown me that the T-Mobile's HSPA+ network is absolutely comparable to LTE. There are only very slight insignificant differences in the tests - some a few degrees higher, some a few lower - according to the tester's location, device, and environment. But they always come extremely close to the same numbers. I've heard LTE does eat a lot of battery, but that's (as always) depending upon individual usage. The SGS III, from what I understand, is capable of supporting LTE, even on the T-Mo model, it's just not being used since they aren't on it, so if/when they do go LTE, your phone will support it. Until then, I think you'll be just as happy with their network. I hope that helps ya! At least I'd feel like I accomplished something with my endless hours lookin at all this crap! Good luck!

Thanks. I ended up going with the SGS 3. So far I like it a lot, its very fast. I am coming from a SGS Vibrant with Slim ICS ROM on it, so I had to install a launcher to get rid of TouchWiz (currently Im using Nova Launcher).

U'll love it!
androidmonkey said:
Thanks. I ended up going with the SGS 3. So far I like it a lot, its very fast. I am coming from a SGS Vibrant with Slim ICS ROM on it, so I had to install a launcher to get rid of TouchWiz (currently Im using Nova Launcher).
Click to expand...
Click to collapse
Oh cool! Me too, had the Vibrant and alternated between 2 ROMs at the end - ICS Passion and Doc's Master, they were both so great! Don't care for TouchWiz at all. I'm currently using Apex right now, it's simple, quick n user-friendly, and comes with the customizing I like - plus it has the capability of running themes from other home launchers, ie; GoLauncher, which I think is friggin awesome! Check it out if ya haven't already, there's not a whole lot it CAN'T do! Anyway, I think you'll LOVE this phone! I never in a million years thought I'd part ways with the Vibrant! I'm really stoked, now that I know how to do everything! If u have any questions, need help with dev stuff, or u just want recommendations, like I said - bored, not much of a life here, so helping is no problem at all! I've been through XDA quite extensively, so I know pretty much all there is to know about the 2 devices I have, just have the noob status still cuz I never post! So feel free to ask anytime! Have fun!!

crayzeeteri said:
Oh cool! Me too, had the Vibrant and alternated between 2 ROMs at the end - ICS Passion and Doc's Master, they were both so great! Don't care for TouchWiz at all. I'm currently using Apex right now, it's simple, quick n user-friendly, and comes with the customizing I like - plus it has the capability of running themes from other home launchers, ie; GoLauncher, which I think is friggin awesome! Check it out if ya haven't already, there's not a whole lot it CAN'T do! Anyway, I think you'll LOVE this phone! I never in a million years thought I'd part ways with the Vibrant! I'm really stoked, now that I know how to do everything! If u have any questions, need help with dev stuff, or u just want recommendations, like I said - bored, not much of a life here, so helping is no problem at all! I've been through XDA quite extensively, so I know pretty much all there is to know about the 2 devices I have, just have the noob status still cuz I never post! So feel free to ask anytime! Have fun!!
Click to expand...
Click to collapse
Thanks, I installed Apex last night. I might buy the Pro version if it becomes my fav. I was on the fence about waiting to get the HTC One X+ that is rumored to be released at the end of Sept. Since I have a track record with Samsung and its a very popular device (more support from devs), I decided to go with Samsung again. The only thing I really need right now is ROOT. I watched a video on Youtube and it looks like its a fairly simple process, not as easy as the Vibrant though. I mainly need ROOT to install Titanium Backup. I'm still confused though about the "flash counter" that some people mention and how Tmo/Samsung can see that you flashed your device if it were sent in for replacement/repair. Any ideas on that?

androidmonkey said:
Thanks, I installed Apex last night. I might buy the Pro version if it becomes my fav. I was on the fence about waiting to get the HTC One X+ that is rumored to be released at the end of Sept. Since I have a track record with Samsung and its a very popular device (more support from devs), I decided to go with Samsung again. The only thing I really need right now is ROOT. I watched a video on Youtube and it looks like its a fairly simple process, not as easy as the Vibrant though. I mainly need ROOT to install Titanium Backup. I'm still confused though about the "flash counter" that some people mention and how Tmo/Samsung can see that you flashed your device if it were sent in for replacement/repair. Any ideas on that?
Click to expand...
Click to collapse
It's a counter that counts custom binaries, if serviced by Samsung they may check it and decline warranty. There is a no trip method in the development section that I highly recommend. Right now there is also an app anyways by guru ChainFire called triangle away, that resets the counter. Either way here's the link to the no trip method that is easy as pie for anyone. Enjoy !
http://forum.xda-developers.com/showthread.php?t=1739426

Yep!
androidmonkey said:
Thanks, I installed Apex last night. I might buy the Pro version if it becomes my fav. I was on the fence about waiting to get the HTC One X+ that is rumored to be released at the end of Sept. Since I have a track record with Samsung and its a very popular device (more support from devs), I decided to go with Samsung again. The only thing I really need right now is ROOT. I watched a video on Youtube and it looks like its a fairly simple process, not as easy as the Vibrant though. I mainly need ROOT to install Titanium Backup. I'm still confused though about the "flash counter" that some people mention and how Tmo/Samsung can see that you flashed your device if it were sent in for replacement/repair. Any ideas on that?
Click to expand...
Click to collapse
Yeah, I bought the Apex Pro, and I don't normally buy many paid apps - I just really like how easy it is to integrate with other things like themes, which I mentioned earlier, and then other things too, ie; lockscreen apps, status bar apps, fonts, icons...so even if I want just one thing different that Apex doesn't have, I can still get that thing and use Apex at the same time!
Rooting!! OK here's what I did, and not a single problem! This is the fastest, easiest time I have ever had rooting and/or flashing by a MILE! I was leery due to the IMIE issues being reported and also, like you, the flash counter voiding the warranty. (if anything happened and I was out of an almost $700 phone, I'd be seriously PISSED!!) So if you do decide to root and/or flash, I would HIGHLY recommend doing these things! 1st, go here: http://forum.xda-developers.com/showthread.php?t=1804123 and back up your IMEI. Just follow the instructions (super simple) to make a backup. I don't think u need to do a full NV backup (u'll understand what that means if u read thru the posts on this issue, but it doesn't matter) because you'll already have your IMEI backed up beforehand. I did it anyway tho, just because I felt safer that way. Up to you! Bookmark that thread tho, in case you ever encounter any IMEI or data probs cuz they're the go-to guys for that, and have all the RIGHT fixes! You'll see the other guy I'm referring to's method and a link to his thread referenced there, where there's a lot more background info, but the guy's thread I gave you the link for is WAY easier for performing the backup. As far as checking the backup to be sure it's there, that can get confusing - If you followed the directions, I promise it worked, just gets techie when trying to read phone stuff on a PC. All info on the subject is in those 2 threads, you'll see it! N E way, do that FIRST BEFORE ANYTHING!!
Next, go here: http://forum.xda-developers.com/showthread.php?t=1746682 and install this to your PC. This is the coolest thing ever to get you backed up, rooted, flashed, whatever. It's called the "Snapdragon Toolkit" I cannot begin to say enough about it! It does EVERYTHING you need - installs the correct drivers, roots, unroots, flashes ROMs, gives u ClockworkMod Recovery AND Odin, and also gives you a full perfect backup - Nandroid backup for CM, .tar file for ODIN - of your stock firmware to keep on your PC in case you run into an issue or just decide to go back to stock. Also provides a walk-thru for resetting the flash counter back to zero using an app called Triangle Away by Chainfire!! It gets u into download mode, roots, gives you Superuser, busybox, CWM, all necessary root stuff, and reboots your phone all automatically in just a quick click! You might have read secure vs insecure kernels - gives you the choice. Insecure leaves you rooted. You can also use it to just kind of temp-root to do something that like say, requires ADB (which requires you to be rooted to use) Do it thru the toolkit, and it will get you (for instance for adb access) the insecure kernel alone, temporarily, until you're done with your task. You can do each thing separately like that or everything all at once. His thread, as well as inside the toolkit itself, when you open it on your PC, gives you total kindergarten instructions and explanations for each thing it does. I have never seen a faster, simpler, more user-friendly program for getting these things done - and all in one place! So get that, and per the instructions, open it and install the drivers 1st before plugging in your phone with ur USB. You probably have the right drivers already, but just in case there are extra drivers there needed for the program or anything it does, I'd go ahead and install them. It'll then open a window that looks old DOS command-line like, and will ask which model you have. Every time you're making any choice in the program, you'll be typing your answer at the bottom of the screen and hitting "enter" to submit. Type the number 3, it's the one for T-Mo T999 UVALEM, and hit enter. It then displays the menu with the list of all the options. You can plug in to be sure the phone's detected, and check it by looking at the top of the window; it'll show it under "List of devices attached." If you do what I did, which was the all-at-once option, you'll hit the number 2 and enter for thr rooting options menu, then 3, enter to choose all-in-one and follow the on-screen instructions for when to plug in the phone and such.
To simplify things further, so you can save some time, I've got all the files you need already, to do your IMEI backup, stock firmware backup,(the Nandroid copy of the firmware and the .tar ODIN copy), the drivers, the most recent ClockworkMod Touch and ODIN files, the Toolkit, and all the .apk files of the apps that are safe to remove from the original firmware if you want that. I didn't remove all of these, for the same reason I haven't flashed AOKP or CM9/CM10 yet; I'm not sure I want to lose the new Samsung stuff like SVoice and the motion features. It's a list others comprised, actually probably really outdated, containing the ones confirmed safe to remove. I just kept in case I wanted any of 'em back! I can personally confirm all the T-Mobile ones, ChatOn, Flipboard, all the Yahoo stuff, self, factory and LCD tests, Samsung's Media Hub, Game Hub, SSuggest, and More Services, Google's Books, Music, TV/Movies, Talk, and Google+(Plus One), Amazon, Polaris Viewer, Facebook SMS, and the system Music and Video apps. I say probably outdated cuz I'm sure the Maps from Google and Samsung, the Cloud sync apps from them all, and the Email apps, for example, are all fine to go too, and probably verified by now. (I mean seriously, do I need Samsung, T-Mo, Google+, GMail, Dropbox, Sugarsync, AND Facebook ALL syncing my stuff?! JEEZUSS!!!) Anyway, all the files are in my dropbox here:
https://www.dropbox.com/sh/8f2wjlz1enkb8wp/saTe7MW0fE
There's also a way to flash CWM Touch Recovery without having to pay for Rom Manager Premium and without tripping the flash counter in there with instructions if you want it, but you have to be ok with entering command line script with adb or a terminal emulator. I just used the Triangle Away app, worked perfect!
Whew! What a novel, huh?! Just wanted to be sure I was thorough so you or anyone reading has specifics so there are no problems for you! I honestly didn't have a single hiccup, and all of it took less time than it's probably gonna take u to read this post! Have fun!

[Q] Where we stand on AOSP?

Basically, I was wondering where we stand in terms of perfectly stable 4.4.2 AOSP builds. I have seen posts saying that there are issues with the LS980 variant in particular, and I am a bit uneasy where we will be down the road, not just for KitKat. Basically, will we get screwed and not be able to go further unofficially(because I fully expect LG to not update past 4.4.X, because it's LG)? I see builds being attempted with 4.4.2 source, but apparently the LS980 will not boot on the newer source. I am contemplating switching to a Nexus 5, as I find myself using AOSP exclusively, but the G2 is better in almost every conceivable way. It's been awkwardly silent for a couple weeks now, so any updates to report? I'm not looking for an ETA, just a possible confirmation of progress. I just want to know if I need to entertain the idea of getting a N5. :silly: Thanks!

Koopa777 said:
Basically, I was wondering where we stand in terms of perfectly stable 4.4.2 AOSP builds. I have seen posts saying that there are issues with the LS980 variant in particular, and I am a bit uneasy where we will be down the road, not just for KitKat. Basically, will we get screwed and not be able to go further unofficially(because I fully expect LG to not update past 4.4.X, because it's LG)? I see builds being attempted with 4.4.2 source, but apparently the LS980 will not boot on the newer source. I am contemplating switching to a Nexus 5, as I find myself using AOSP exclusively, but the G2 is better in almost every conceivable way. It's been awkwardly silent for a couple weeks now, so any updates to report? I'm not looking for an ETA, just a possible confirmation of progress. I just want to know if I need to entertain the idea of getting a N5. :silly: Thanks!
Click to expand...
Click to collapse
UMMMM what???? cm11 works great!

Robisgnarly said:
UMMMM what???? cm11 works great!
Click to expand...
Click to collapse
Sure, except for the poor audio quality, random reboots, system lockups, GPS issues, some apps not working with touchscreen, etc.....
So yeah, except for all AOSP ROMs being completely unstable and borderline unusable, they're pretty solid.

Koopa777 said:
Sure, except for the poor audio quality, random reboots, system lockups, GPS issues, some apps not working with touchscreen, etc.....
So yeah, except for all AOSP ROMs being completely unstable and borderline unusable, they're pretty solid.
Click to expand...
Click to collapse
had better audio quality on cm11 than stock 4.2.2, my phone never randomly rebooted, never locked up unless i caused it..... never had these issues.. so i guess i was one of the lucky ones?

Koopa777 said:
Sure, except for the poor audio quality
Click to expand...
Click to collapse
nope, sounds identical here.
Koopa777 said:
random reboots
Click to expand...
Click to collapse
once every two weeks or so when an app locks up is not "random reboots" and 100% not the fault of CM11
Koopa777 said:
system lockups
Click to expand...
Click to collapse
see above, 100% BS statement.
Koopa777 said:
GPS issues
Click to expand...
Click to collapse
already multiple solutions posted for that:
1: put it in 3g only mode
2: set it to "device only"
Koopa777 said:
some apps not working with touchscreen, etc.....
Click to expand...
Click to collapse
Got any proof of that? everything's been 100% working here. Even FM works great with Spirit 2.
Koopa777 said:
So yeah, except for all AOSP ROMs being completely unstable and borderline unusable, they're pretty solid.
Click to expand...
Click to collapse
Summary: go away troll, not unless you have proof of anything you say.

Fnord12 said:
nope, sounds identical here.
once every two weeks or so when an app locks up is not "random reboots" and 100% not the fault of CM11
see above, 100% BS statement.
already multiple solutions posted for that:
1: put it in 3g only mode
2: set it to "device only"
Got any proof of that? everything's been 100% working here. Even FM works great with Spirit 2.
Summary: go away troll, not unless you have proof of anything you say.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2474887
http://forum.xda-developers.com/showthread.php?t=2601467
http://forum.xda-developers.com/showthread.php?t=2630977
http://forum.xda-developers.com/showthread.php?t=2485088
http://forum.xda-developers.com/showthread.php?t=2677295
From a well-known dev:
"Like most kitkat roms actions from superuser / power up bluetooth *can* cause lag until you screen off and on.
D802 and VS980 have reboot issues like every other rom. Please do not report this or ask other users if they also get them, its a well known issue." - dr87
Audio issues can be found in literally every single ROM thread, I wasn't wasting more of my time finding quotes.
Every AOSP ROM has these issues, period. Whether or not you get them is a roll of the dice, but saying they don't exist shows how out-of-touch with the community you really are. Maybe try learning about the device you use, and know what you're talking about before you attack other members of the community. If I'm wrong fine, tell me I'm wrong, I'll respect and understand that. But when 5 minutes of searching generates all that "proof", much less what has been documented since August, it shows that you clearly would rather attack others than educate yourself.

Robisgnarly said:
had better audio quality on cm11 than stock 4.2.2, my phone never randomly rebooted, never locked up unless i caused it..... never had these issues.. so i guess i was one of the lucky ones?
Click to expand...
Click to collapse
It depends, LiquidSmooth has been stable for me recently, I got two freezes 2 weeks ago, but none since. Touch screen is borked for certain apps on all AOSP ROMs though, regardless. All ROMs have these issues, but it varies on the severity. I have personally never had stable GPS on ANY AOSP ROM since I got the phone on release day(November 8th), and I've tried every ROM available for the LS980.
These issues are supposed to be fixed in newer ROMs incorporating 4.4.2 kernel source, but the LS980 is struggling to boot said source, from what I understand. Check out houstonn's PA 4.0 or dr87's Mahdi, both are testing builds with newer source, and all these issues are apparently fixed. :good:

Koopa777 said:
http://forum.xda-developers.com/showthread.php?t=2474887
http://forum.xda-developers.com/showthread.php?t=2601467
http://forum.xda-developers.com/showthread.php?t=2630977
http://forum.xda-developers.com/showthread.php?t=2485088
http://forum.xda-developers.com/showthread.php?t=2677295
From a well-known dev:
"Like most kitkat roms actions from superuser / power up bluetooth *can* cause lag until you screen off and on.
D802 and VS980 have reboot issues like every other rom. Please do not report this or ask other users if they also get them, its a well known issue." - dr87
Audio issues can be found in literally every single ROM thread, I wasn't wasting more of my time finding quotes.
Every AOSP ROM has these issues, period. Whether or not you get them is a roll of the dice, but saying they don't exist shows how out-of-touch with the community you really are. Maybe try learning about the device you use, and know what you're talking about before you attack other members of the community. If I'm wrong fine, tell me I'm wrong, I'll respect and understand that. But when 5 minutes of searching generates all that "proof", much less what has been documented since August, it shows that you clearly would rather attack others than educate yourself.
Click to expand...
Click to collapse
lessee here:
link 1: not AOSP or CM11
link 2: an uber *tiny* minority that could just as easily not like 4.4.x
link 3: very old thread, doesn't reflect current CM11 roms
link 4: not relevant, this is the sprint section and I see almost no CM11/AOSP mentions there. Last AOSP mention was in December... aka: doubly not relevant
link 5: very not relevant as that's a VZW G2 and not a sprint one. (this is the SPRINT section afterall) Doubly not relevant due to mentions in the thread you linked to mentioning the vzw G2 is the crippled version.
aka: go away, troll.

Fnord12 said:
lessee here:
link 1: not AOSP or CM11
link 2: an uber *tiny* minority that could just as easily not like 4.4.x
link 3: very old thread, doesn't reflect current CM11 roms
link 4: not relevant, this is the sprint section and I see almost no CM11/AOSP mentions there. Last AOSP mention was in December... aka: doubly not relevant
link 5: very not relevant as that's a VZW G2 and not a sprint one. (this is the SPRINT section afterall) Doubly not relevant due to mentions in the thread you linked to mentioning the vzw G2 is the crippled version.
aka: go away, troll.
Click to expand...
Click to collapse
I was going to continue to defend, but then I thought, "why?" I'll leave you with something equally irrational.
"Walrus pancakes taste good with maple syrup."
Blocked.

So Android 5 LOLLIPOP has been officially revealed...

...and will it come out to our GNex ? :3
The SDK is coming out on Oct 17 (Source: http://www.androidpolice.com/2014/10/15/the-android-5-0-lollipop-sdk-will-arrive-on-october-17th/)
I hope so, because of the new GPU drivers in the FML-ROM, we're "prepared" for it(?)

When the source code will come out I'm sure that the develepers will start do work on it

devil188 said:
...and will it come out to our GNex ? :3
The SDK is coming out on Oct 17 (Source: http://www.androidpolice.com/2014/10/15/the-android-5-0-lollipop-sdk-will-arrive-on-october-17th/)
I hope so, because of the new GPU drivers in the FML-ROM, we're "prepared" for it(?)
Click to expand...
Click to collapse
We are, but we wont port sdk, we will w8 to opensource dorp

does this mean that Samsung Galaxy Nexus will have a version of Lollipop developed for it?

blekm said:
does this mean that Samsung Galaxy Nexus will have a version of Lollipop developed for it?
Click to expand...
Click to collapse
not sure if didn't read other responses, or just being smart-aleck
lulz
but...
it is a POSSIBILITY
NOTHING can be CERTAIN until source drops AND someone TRIES, but I'd have to IMAGINE that SOMEONE will be trying hard as HELL to keep this device rolling in development no matter how old it gets, many people hold this device dear to their hearts, it was one of the first WIDELY released nexus devices on MULTIPLE carriers including cdma. and even though it's a pita sometimes, we still have love for this ol girl, but right now, at this very moment, NO ONE can tell you 100% if it WILL run lollipop %100 stable or even what many would consider daily driver type of builds.
have I answered the question yet that's been asked a couple times and answered already just not in as many words? I'm NOT trying to be a ****, I REALLY would like to know if anyone is still confused about this situation?

you've tried really hard to be a ****, though
I haven't read others, I don't frequent this forum often, I'm not into custom ROMS.
I was just passing by asking this info. On this post there was nothing that explained the situation as you did. And there were no info on the first page of the Galaxy Nexus forum.
Thanks, it's a bit more clear. I'll drop by in a few months to see what's happening

Android 4.4 wasn't officially supported by Galaxy Nexus, yet we have a plethora of ROMs to choose from. I believe that 5.0 will be no different. It will take more time to get it to work because of the changes from other iterations, but we will get it. Not officially. Google probably won't give a hoot that there is a new driver, and just leave the device for dead. There is no money to be made from the amount of work that would have to be done. If it DOES get officially released, I'd be incredibly surprised.

blekm said:
you've tried really hard to be a ****, though
I haven't read others, I don't frequent this forum often, I'm not into custom ROMS.
I was just passing by asking this info. On this post there was nothing that explained the situation as you did. And there were no info on the first page of the Galaxy Nexus forum.
Thanks, it's a bit more clear. I'll drop by in a few months to see what's happening
Click to expand...
Click to collapse
yep, that tends to happen when I go posting after a few beers, apologies, but hey, I cleared it up right? that was really my main intention

fxxk it. we didnt even get kikat. The lollipop isn't for Gnex and I doubt google is going to do it . if they really are this "generous", I will bang my head against the wall just to make sure I aint dreaming!

randy6644 said:
fxxk it. we didnt even get kikat. The lollipop isn't for Gnex and I doubt google is going to do it . if they really are this "generous", I will bang my head against the wall just to make sure I aint dreaming!
Click to expand...
Click to collapse
NO ONE has said that Google will push ANY kind of official L update to gnex, when source code drops, custom Rom development will undergo to try and bring 5.0 based aosp roms to the gnex, which isn't unfeasible.

ashclepdia said:
NO ONE has said that Google will push ANY kind of official L update to gnex, when source code drops, custom Rom development will undergo to try and bring 5.0 based aosp roms to the gnex, which isn't unfeasible.
Click to expand...
Click to collapse
I heard of CM is not going to support galaxy nexus with lollipop due to the lack of maintainers. Maybe teams like PA might keep on with their supports. But I don't expect Gnex would run well on L coz it doesn't even on Kitkat. every now and then I see stuters and bugs . When I thought Gnex was dying and apparently showing its age, I flashed back to the stock 4.3 . The magic just happened and my gnex was brought back to life . yes the scrolling isn't as smooth as that on others roms but everything is fast especially when it comes to multitasking, it's great.
with that said , I mean even gnex is going get supports from some devs , what we could do with it is simply have a look at that and that will by no means be a stable and pleasant daily driver.

randy6644 said:
I heard of CM is not going to support galaxy nexus with lollipop due to the lack of maintainers. Maybe teams like PA might keep on with their supports. But I don't expect Gnex would run well on L coz it doesn't even on Kitkat. every now and then I see stuters and bugs . When I thought Gnex was dying and apparently showing its age, I flashed back to the stock 4.3 . The magic just happened and my gnex was brought back to life . yes the scrolling isn't as smooth as that on others roms but everything is fast especially when it comes to multitasking, it's great.
with that said , I mean even gnex is going get supports from some devs , what we could do with it is simply have a look at that and that will by no means be a stable and pleasant daily driver.
Click to expand...
Click to collapse
I'm looking to go back to 4.3 as well. Is it as simple as doing the normal procedures and flash a 4.3 rom? I heard of some issues downgrading while using 4.4 bootloaders and problems with SD card memory. Just want to make sure if there were any extra precautions you had to take before going back to 4.3

randy6644 said:
I heard of CM is not going to support galaxy nexus with lollipop due to the lack of maintainers. Maybe teams like PA might keep on with their supports. But I don't expect Gnex would run well on L coz it doesn't even on Kitkat. every now and then I see stuters and bugs . When I thought Gnex was dying and apparently showing its age, I flashed back to the stock 4.3 . The magic just happened and my gnex was brought back to life . yes the scrolling isn't as smooth as that on others roms but everything is fast especially when it comes to multitasking, it's great.
with that said , I mean even gnex is going get supports from some devs , what we could do with it is simply have a look at that and that will by no means be a stable and pleasant daily driver.
Click to expand...
Click to collapse
just the toro and toroplus variants.
maguro still maintained
so for someone to build for toro/toroplus isn't too much to infer. I can't see NO ONE not building for gnex at Some point
whether EVERYTHING is FULLY working or not is another story, but I'm sure it'll be usable

Mikey503 said:
I'm looking to go back to 4.3 as well. Is it as simple as doing the normal procedures and flash a 4.3 rom? I heard of some issues downgrading while using 4.4 bootloaders and problems with SD card memory. Just want to make sure if there were any extra precautions you had to take before going back to 4.3
Click to expand...
Click to collapse
No, there's not a single problem that i've seen. I just downloaded the factory Image and flashed it in fastboot mode.
but that will erase everything so just make a backup for your apps.

Funny that you say 4.3 runs well on your gnex because I've been running stock 4.3 for quite a while because I was fed up with trying to find the best custom rom and dealing with kernels and stuff.
4.3 runs like complete **** on my gnex and it has since I put it on there. It seems to get worse as time goes on though. I was using the Aviate launcher for quite a while but just installed the Google Now one to try that out and it seems much, much worse than Aviate in the performance department. I can be in an app, press home button and it will be close to 10 seconds sometimes for it to load, even with no apps present in the multitask/app switch thing. Blows my mind. I don't know why the performance is so bad.
I want to go back to android 4.1.2 because it's the only time I remember my gnex being quick.....but im having a hard time making that decision because of feature reasons.

naossoan said:
Funny that you say 4.3 runs well on your gnex because I've been running stock 4.3 for quite a while because I was fed up with trying to find the best custom rom and dealing with kernels and stuff.
4.3 runs like complete **** on my gnex and it has since I put it on there. It seems to get worse as time goes on though. I was using the Aviate launcher for quite a while but just installed the Google Now one to try that out and it seems much, much worse than Aviate in the performance department. I can be in an app, press home button and it will be close to 10 seconds sometimes for it to load, even with no apps present in the multitask/app switch thing. Blows my mind. I don't know why the performance is so bad.
I want to go back to android 4.1.2 because it's the only time I remember my gnex being quick.....but im having a hard time making that decision because of feature reasons.
Click to expand...
Click to collapse
It gets worse because the Java garbage colector is not doing what it's suppose to do and you have memory leaks so the memory gets full without a way of emptying it... To get around this, you need to restart the phone to empty the memory(usually daily or even two times a day). This HUGE bug is present onward since 4.2 for GNex, excluding 4.4 builds. So 4.1.2 will be best in that department.
But there is no need to go back to 4.1.2 to get this fixed (I couldn't bare it). Instead CM 10.1 has managed to fix the leak and you would be on 4.2 which is pretty similar to 4.3 and even 4.4 from the user end

I think Android 5.0 unofficially will continue.
There will be no further support officially. I "travel" too in different kit kat roms but always there were a bit of lag.
I return to cm 10.2 and my phone was brilliant, pretty quick.
Until recently that I install liquidsmooth that gone very fast for kit kat version.
I think now the kit kat versions will be enough stable. For lollipop, we will have to wait a lot.
we will see.

Source code just been released, so anyone working on, thx

I want cm lolipop!!!

The moment is arrived! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
Sent from my Galaxy Nexus using XDA Free mobile app