• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] removed

Status
Not open for further replies.
xstefen said:
Anyone figure out how to make bittorrent not suck on the phone. On wifi. Not even getting a a kB/s
Click to expand...

kyky78 said:
stalking thread for direct download link!
Click to expand...

TeachMe said:
With bit being a seed program setup new downloads like this are always slow until lots of people have and are sharing it.
Click to expand...

The problem, as usual, lies with my crappy internet connection. Whether I'm seeding on bit torrent or not, 9 times out of 10 the upload to AFH fails. Even though it says successful, the md5 sums don't match. It was much easier before we killed rbheromax's FTP server because FileZilla never failed to properly upload a file. Sorry for the slow speeds, everyone. Bear with it and it'll go faster when more people can seed (like TeachMe said). Eventually the direct link will be up but knowing my luck (and Time Warner's service), not until tomorrow at the earliest.

On a more personal note, I've been cleared to return to work around the 12th as long as my condition continues to improve so I may not be around as much as I have been. I'll do my best to answer any questions that pop up, and I want to thank everyone that helps out when I'm unable to, and a special thanks to TeachMe for all the help you've given me.
 
If you got an account with mega.co.nz do you think there would be traffic limits? You get a free 50 GBP, direct download and I've never had failed uploads.
 
NolenUmar said:
If you got an account with mega.co.nz do you think there would be traffic limits? You get a free 50 GBP, direct download and I've never had failed uploads.
Click to expand...

AFH is not the problem. What happens is sometimes the connection drops on my side during the upload process. Web-based uploaders tend to view this as either an incomplete (failed) upload or as an end-of-file (which results in a corrupt file). With rbheromax's server, I had a direct FTP connection which supported resumable uploads. FileZilla (my FTP client of choice) would detect my connection loss, pause the upload, and resume it when the connection stabilized.

As a side-note, I haven't forgotten about you and I'm still trying to figure out the whole issue with getting this working on Sprint. Without a Sprint phone to test it on, it's slow going and a lot of file comparison.
 
Fifty downloads of the zip file and 43 of the torrent file and no bugs reported? :) One of my biggest goals with this release was to get it as stable as I possibly could before I go back to work and don't have as much time to work on it. Looks like a resounding success.

Incidentally, I have not only met, but far exceeded my original design goal: to have as close to a stock AOSP/Google experience as could be achieved, since it appears that CyanogenMod is currently beyond our reach and may never fully work due to the weird way our phones access Sprint's LTE network (this causes issues with MMS, which I believe I have detailed elsewhere).

Anyway, it's not likely that there will be any more huge updates to the ROM, barring some new feature that I stumble across that I feel like implementing (actually, there is one, but it is a very long and tedious process and likely won't be completed for a while). Updates will still come as bugs are found and squashed, and of course I'll be working on themes. The three I am looking into are a light green (Holo green) recolor of the default theme, a Sense 4 or 5 theme, and a KitKat theme. So that's what the status of the ROM is. It's stable, works for pretty much everybody, and it has some nice themes available and in development.
 
moonknightus said:
Fifty downloads of the zip file and 43 of the torrent file and no bugs reported? :) One of my biggest goals with this release was to get it as stable as I possibly could before I go back to work and don't have as much time to work on it. Looks like a resounding success.

Incidentally, I have not only met, but far exceeded my original design goal: to have as close to a stock AOSP/Google experience as could be achieved, since it appears that CyanogenMod is currently beyond our reach and may never fully work due to the weird way our phones access Sprint's LTE network (this causes issues with MMS, which I believe I have detailed elsewhere).

Anyway, it's not likely that there will be any more huge updates to the ROM, barring some new feature that I stumble across that I feel like implementing (actually, there is one, but it is a very long and tedious process and likely won't be completed for a while). Updates will still come as bugs are found and squashed, and of course I'll be working on themes. The three I am looking into are a light green (Holo green) recolor of the default theme, a Sense 4 or 5 theme, and a KitKat theme. So that's what the status of the ROM is. It's stable, works for pretty much everybody, and it has some nice themes available and in development.
Click to expand...

This is precisely what stumped me in trying to build Omni for it after attempting to borrow the CM10.2 kernel source...
 
Yeah I've given up on it as well. And my kernel as you and Teachme and other contributers have truly made this an awesome possibility for our phone. I will dev again when the N5 comes out if I get that or one of the official CM phones. Great work all of you and especially you moon for putting this together. Thanks
 
kwknott said:
Moon the new rom has ran without any issues. I did have the bluetooth bug but I installed teach's fix you sent me and rolling right along now
Click to expand...

Weird. Bluetooth fix should've been included in this one. As long as it's working for you, I guess it's all good.
 
Well, I've left a link up to TeachMe's bluetooth fix and updated the FAQs to reflect this.

I have a new MMS fix that may enable using 3rd-party MMS apps in standalone mode (ie. 8sms, GO SMS, Google Hangouts). I tested it and it works on my phone in both CDMA-only and CDMA+LTE modes, but since I don't have LTE service in my area, I still cannot test sending MMS over LTE. This fix is not Conquest-specific and should be compatible with any stock-based ROM, odexed or deodexed (including Victorious). The fix is based on MopedRyder's work here. Any LTE-enabled volunteers to test?

Please bear in mind that in testing this you may lose LTE functionality until you do a complete system wipe and re-install.
 
I have a question. Rest driving the Google Launcher and I was moving icons to different screens and when I moved the last icon I lost the screen. I'm down to 2. How do I add another screen?
 
buzzcon said:
I have a question. Rest driving the Google Launcher and I was moving icons to different screens and when I moved the last icon I lost the screen. I'm down to 2. How do I add another screen?
Click to expand...

Did 9.0 work for you? :-)

Anyway, to add a new screen, drag an icon to the right of the right-most screen. The only screen you can add to the left is the Google Now screen, and that's done by enabling Google Now in settings.
 
Test results are in. This still doesn't work on 4G so I'm not going to include it in an update or as a flashable at this point. I'll let you all know if anything changes or if I need any more testers.
 
touchwiz launcher not working on 9.0,it installs perfect. lock screen shows but when i unlock it,its a black screen,and i did wipe sys,data and both caches. i only got the google launcher to work on 9.0
 
Status
Not open for further replies.
Back
Top Bottom