Related
ICS has also now been ported and boots up on the Droid 3 lol. Great work to Hashcode for getting it going!
http://hash-of-codes.blogspot.com/2011/11/you-got-your-ice-cream-on-my-droid-3-no.html
Well, it is a 3G phone, so there shouldn't be issues getting the radios working. I do find it amusing the type of the support these cheesy phones get though.
I don't want to get off topic, but I am curious what sort of CIQ and other potential spyware has been implemented in ICS. It seems a good opportunity for Google to embed CIQ deep within the framework, but alas, who knows.
The main two features of ICS that I think I would like, but don't need, is USB OTG and WiFi Direct.
spc_hicks09 said:
ICS has also now been ported and boots up on the Droid 3 lol. Great work to Hashcode for getting it going!
http://hash-of-codes.blogspot.com/2011/11/you-got-your-ice-cream-on-my-droid-3-no.html
Click to expand...
Click to collapse
Smh we will never see it
I keep hearing we won't have ics because we have a 4g phone but the bionic just got ics port... Maybe we still have hope?
Sent from my SCH-I510 using XDA App
mikehal38 said:
I keep hearing we won't have ics because we have a 4g phone but the bionic just got ics port... Maybe we still have hope?
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Very good point!!!!
I'm one person, would you rather have me work on getting a good ROM out based on stock TW, or go to work on what may never be a fully functional AOSP build? If you want it so bad, no one here is going to stop you from taking up the work on your own...
imnuts said:
I'm one person, would you rather have me work on getting a good ROM out based on stock TW, or go to work on what may never be a fully functional AOSP build? If you want it so bad, no one here is going to stop you from taking up the work on your own...
Click to expand...
Click to collapse
Don't do it because of us! Do what you enjoy doing and share with us because your proud of your work.
I
imnuts said:
I'm one person, would you rather have me work on getting a good ROM out based on stock TW, or go to work on what may never be a fully functional AOSP build? If you want it so bad, no one here is going to stop you from taking up the work on your own...
Click to expand...
Click to collapse
You already know. Yes, we are eager for ICS/CM7.1/CM7.2/CM9...and everything under the sun that a working RIL would enable us. But, having said that, I think the vast majority of us place FUNCTION in front of FEATURES.
We, Android enthusists with the skills to flash but not actually dev, are like children and will never be satisfied. We need a healthy meal, but are going to whine to have candy for dinner every night. As a dev, you're more similar to our parent in this metaphor... Don't take it personally when we metaphorically say we hate you--we don't. We love you. We need your help to eat at all, so make sure it's the best meal you can provide.
Besides, if the RIL never comes, who bought this phone for Ice Cream Sandwich anyway? I bought this phone for 4G.
imnuts said:
I'm one person, would you rather have me work on getting a good ROM out based on stock TW, or go to work on what may never be a fully functional AOSP build? If you want it so bad, no one here is going to stop you from taking up the work on your own...
Click to expand...
Click to collapse
imnuts, please don't take my post or the title the wrong way. I am in now way at all saying anything bad about what you do for this phone. Your work is very highly regarded in my book. I was just pointing out how crazy it is with all these ICS ports coming out now. I can promise you that I am grateful for all the work you do for us.
If you want an AOSP ROM, you shouldn't buy a Samsung phone.
Twice bitten for me. Neither of my Samsung phones has had an AOSP ROM.
As a self-proclaimed nube, I am generally curious what advantages we would see on AOSP anyways.
Is there some super-spiffy amazing bad-ass feature that I don't know about?
Humble 5.0 is great for me. I will try Infinity if/when its ready.
ICS in particular has WiFi Direct and USB OTG as I mentioned above, which I assume that CM7 wouldn't enable.
xdadevnube said:
As a self-proclaimed nube, I am generally curious what advantages we would see on AOSP anyways.
Is there some super-spiffy amazing bad-ass feature that I don't know about?
Humble 5.0 is great for me. I will try Infinity if/when its ready.
ICS in particular has WiFi Direct and USB OTG as I mentioned above, which I assume that CM7 wouldn't enable.
Click to expand...
Click to collapse
AOSP tends to offer a faster experience, and better battery life. It does this by not having any carrier or OEM bloat anywhere. There is a lot of stuff added on to the stock ROM that cannot be removed. To give you an idea, a heavily debloated TW ROM for the Fascinate is usually ~160MB, give or take, where as a stock AOSP ROM is <100MB for the same Android version, GB in this case. That would mean that even the best debloated/cleaned up TouchWiz ROM is still going to have about 40% more useless junk in it than a stock AOSP ROM, and that junk slows down the system and drains the battery.
mikehal38 said:
I keep hearing we won't have ics because we have a 4g phone but the bionic just got ics port... Maybe we still have hope?
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Bionic got ICS support because Kejar has a Bionic probably. I'm just glad we are on the eve of GB finally and that Imnuts and Imoseyon can get to business with some code.
Over the years around computers I've learned one thing, the next OS is always easier to use, easier to program in and what not, but it is always more complex and requires more hardware, more RAM and shortly after release the end user experience isn't all that much better than it was 6 months earlier. You should see DOS 5 run on a quad core monster processor - wow!
Droidianslip said:
Bionic got ICS support because Kejar has a Bionic probably. I'm just glad we are on the eve of GB finally and that Imnuts and Imoseyon can get to business with some code.
Over the years around computers I've learned one thing, the next OS is always easier to use, easier to program in and what not, but it is always more complex and requires more hardware, more RAM and shortly after release the end user experience isn't all that much better than it was 6 months earlier. You should see DOS 5 run on a quad core monster processor - wow!
Click to expand...
Click to collapse
I agree with what you're saying mostly, but your post almost sounds like you expect Imnuts and Imoseyon to develop and post their work when they have zero obligation to develop and/or share any of their work in any way. If I wasn't so hard-pressed for cash, I would donate more to the devs. I will when I am able though.
One should also remember the short life cycle of smartphones. I am already looking forward to the Galaxy S III mostly for the display- SAMOLED III.
Also, I would like to be able to watch 480p Flash content in the browser without having to overclock, hopefully 720p Flash in the browser with the GS3.
Of course I would like my Charge to blaze along at its maximum potential, but there is a thin line between spending and wasting time on dated hardware. If you want the the best experience on a device, then it would be best to buy older hardware that it well-developed, like the Fascinate. I am willing to sacrifice for the perks of the Charge, like the SAMOLED+ display and 4G.
I was surprised and sad to find that Scott (scrosler) has moved on to a new device (Nexus7, SGS Note2...) and left us with a great ROM (CleanROM v2.4) but with no clear path to the future. I have used Baked Black Bean and Hiemanshu's various offerings and there is lots of potential there, especially with Clemsyn's CM kernels.
What do you say...are you leaning toward CM or AOSP (4.2???) or are you hoping for someone to take over CleanROM and continue with a tweaked stock experience?
I do know that I'm going to focus my donations on Clemsyn to try to get him a TF700 so he can continue to work his kernel magic!
Update: Since this was posted, some great devs stepped up and took over the CleanROM legacy.
Thanks for the great dicussion, guys! :victory:
Honestly, I have no idea yet. I see no reason to flash anything else anytime soon. I'm still very happy with CleanROM (still using 2.3, haven't gotten around to 2.4 yet). I've got my eyes on Paranoid, LiquidSmooth and CM10 though, and will be following the developmentˆˆ
Heck I was fine with 2.3...
Then 2.4 appeared so I'm pretty sure things will be good for a long while.
I'm confident there will be more excellent development coming.
Shipped by rail freight
Firebrazer said:
I see no reason to flash anything else anytime soon.
Click to expand...
Click to collapse
Thats OK said:
I'm pretty sure things will be good for a long while.
Click to expand...
Click to collapse
Asus has released six firmware updates in seven months, so while we're fine now, soon enough we'll need somebody to at least rebase CR 2.4 on new firmware every time there's an update.
Kisakuku said:
Asus has released six firmware updates in seven months, so while we're fine now, soon enough we'll need somebody to at least rebase CR 2.4 on new firmware every time there's an update.
Click to expand...
Click to collapse
...or we use the other great ROMs for our Infinity
sandmann241 said:
...or we use the other great ROMs for our Infinity
Click to expand...
Click to collapse
Which is? Wasn't aware of another stock based ROM. CM10 is great, but I would prefer to have at least one up to date stock based ROM available as an option.
I just caved and unlocked and flashed CleanROM, only to learn the developer left!
Well, it is a much better stock experience, so I should be good for a while, and will follow the development of others ROMs I guess.
Vo01985 said:
I just caved and unlocked and flashed CleanROM, only to learn the developer left!
Click to expand...
Click to collapse
Oh man...I was about to unlock and flash CleanROM last night. Am very, very happy that I didn't now.
Why? CleanROM 2.3 (can't speak for 2.4 since I haven't flashed it yet) is still an absolutely fantastic ROM - that doesn't change just because the developer has moved on to a different device. Granted, there may be no more updates Scott, but I'm still hopefull somebody takes over development. If not, I'll have to keep an eye out for other ROMs.
And if you were "about to" unlock, it's gonna happen sooner or later
Firebrazer said:
Why? CleanROM 2.3 (can't speak for 2.4 since I haven't flashed it yet) is still an absolutely fantastic ROM - that doesn't change just because the developer has moved on to a different device. Granted, there may be no more updates Scott, but I'm still hopefull somebody takes over development. If not, I'll have to keep an eye out for other ROMs.
And if you were "about to" unlock, it's gonna happen sooner or later
Click to expand...
Click to collapse
I wouldn't hesitate to flash CleanROM 2.4, I've been running it for a couple of days and all I can say is WOW, V2.3 was brilliant... V2.4 is ( in my opinion ) a noticeable upgrade and is better again!
Cheers
Glad that I haven't unlocked mine yet. It's true that there should be at least 1 stock based ROM available. I indeed enjoy some of the stock ROM features. I am not moving to CM or AOSP ROM unless they provide a newer Android update than stock.
I've been very happy with clean rom 2.4. I've been running paranoid android on my n7 and it is a super rom. A step up from stock so that is where I will be going next.
i am not a dev...
But i figured i would try to mess around a little
I tried png optimizing cleanrom 2.4 and installing/running v6 supercharger script along with some extra buildprop tweaks
which i found in a tf300t stock based rom...
The device feels a little faster in my opinion and apps launch a little faster(might just be my brain playing games)
i was wondering if someone with the right knowledge would mind to try and png optimize and incorporate v6 supercharger into this rom?
and see if there is any gains?
as i do not know how this would be done as i am a newb
btw these are the build prop lines i added:
dalvik.vm.execution-mode=int:jit
persist.sys.NV_FPSLIMIT = 120
debug.performance.tuning=1
persist.sys.composition.type=gpu
ro.media.enc.jpeg.quality=100
com.qc.hardware=true
ro.debuggable=1
dalvik.vm.verify-bytecode = false
ro.media.dec.jpeg.memcap=80000000
ro.media.enc.hprof.vid.bps=8000000
papand7 said:
i am not a dev...
But i figured i would try to mess around a little
Click to expand...
Click to collapse
I think Scott (and many other devs) started the same as you.
papand7 said:
I tried png optimizing cleanrom 2.4 and installing/running v6 supercharger script along with some extra buildprop tweaks
which i found in a tf300t stock based rom...
Click to expand...
Click to collapse
What do you mean with "png optimizing"? PNG is a graphics format, what's the relation to the Android OS?
papand7 said:
The device feels a little faster in my opinion and apps launch a little faster(might just be my brain playing games)
Click to expand...
Click to collapse
Many of the "optimizations", even some of those in CleanROM, are pure psychology, or the speed increase is real, but only due to rebooting or cleaning data.
papand7 said:
dalvik.vm.execution-mode=int:jit
persist.sys.NV_FPSLIMIT = 120
debug.performance.tuning=1
persist.sys.composition.type=gpu
ro.media.enc.jpeg.quality=100
com.qc.hardware=true
ro.debuggable=1
dalvik.vm.verify-bytecode = false
ro.media.dec.jpeg.memcap=80000000
ro.media.enc.hprof.vid.bps=8000000
Click to expand...
Click to collapse
Now for each of these, find out what they are, and if your setting has any effect at all.
PNG optimize is a way to make all of the apps in the System/apps folder smaller leaving a smaller memory footprint when the device is running,
at least thats what i understand.
well the tweaks i did might just be psychologic but i guess i will never know for sure untill others try it..
i have no clue about all of those build.prop edits and as i said i am not a dev i am just playing around learning a little
But i will try to find out what they are supposed to do
well if scott is picking this one up then that would be awesome!
my device has alot of screen popping aka screen is loose some places...
Have anyone gotten asus to fix issues like this on an unlocked device for free?
papand7 said:
PNG optimize is a way to make all of the apps in the System/apps folder smaller leaving a smaller memory footprint when the device is running,
at least thats what i understand.
Click to expand...
Click to collapse
What does it do? Remove PNGs for unused resolutions? Compress them better?
papand7 said:
i have no clue about all of those build.prop edits and as i said i am not a dev i am just playing around learning a little
But i will try to find out what they are supposed to do
Click to expand...
Click to collapse
You don't need to be a dev to operate a search engine. It just helps to understand the descriptions that you will find. But for example, if you find that the default value of some property is the same you are trying to set, you will have gained knowledge even without understanding what exactly the property does.
_that said:
But for example, if you find that the default value of some property is the same you are trying to set, you will have gained knowledge even without understanding what exactly the property does.
Click to expand...
Click to collapse
And as long as the nose doesn't light up you'll be fine...
CleanROM 2.4 is good to go, and will be for the life of the device. OCD Flashing Disorder is just that, and nothing more. I admit I too suffered from it with my SGS2, but I've come to realize that devicest do not need to run the very latest to just be great in themselves. I'm happy with the TF700 as it is now, and since all the other ROMs fail to properly support the dock, I will not be changing -- at least until the touchpad can be turned off, and the WiFi/Bluetooth/brightness toggles work properly. Those are my minimal criteria.
I'll be sticking to CleanRom2.4 myself for a long while (on 300t). And I completely agree with Marty, there's really no reason to be constantly updating the ROM to the next android version. I haven't updated my SII Rom in months and I have absolutely no issues with it. (The developer also ceased making updates for the SII rom)
Yeah I'm on CleanROM 2.4 and it's very good. It's still a stock experience yet it is much, much faster. I don't have OCD flashing syndrome (probably cause I suck at backupping and restoring). But I should use this ROM for quite a while.
Sent from my ASUS Transformer Pad TF700T
I'm just looking for a fully working custom rom to put on this phone. I need everything working. THis isnt my phoen which is why im not scouring the threads myself. If anyone can help thatll be great.
Try CM10.2 which is the most stable custom ROM for this device. Also, you can try CM11 which is pretty stable too.
ameer1234567890 said:
Try CM10.2 which is the most stable custom ROM for this device. Also, you can try CM11 which is pretty stable too.
Click to expand...
Click to collapse
does 10.2 support wifi calling?
To my knowledge, no custom image for any phone supports Tmobile's current implementation of WiFi Calling. If someone can prove me wrong, I would personally adore it.
That said, Almost any Image can be made to support SIP and VoIP, which is essentially what Tmo's WiFi Calling is, without the ability to use your usual Tmobile mobile number.
Magamo said:
To my knowledge, no custom image for any phone supports Tmobile's current implementation of WiFi Calling. If someone can prove me wrong, I would personally adore it.
That said, Almost any Image can be made to support SIP and VoIP, which is essentially what Tmo's WiFi Calling is, without the ability to use your usual Tmobile mobile number.
Click to expand...
Click to collapse
I'm coming from the HTC G2 and for awhile I had a custom ROM with WiFi calling. Technically I think I had to install it as an addon after I flashed the ROM but it shows it's been done. Here's the original thread where it was posted: http://forum.xda-developers.com/showthread.php?t=1664106. Was able to get WiFi calling on ICS even though there was never a stock ICS ROM for the G2.
So it might be in the realm of possibilities. I do know that the G2 had a lot more dev activity though.
jgummeson said:
I'm coming from the HTC G2 and for awhile I had a custom ROM with WiFi calling. Technically I think I had to install it as an addon after I flashed the ROM but it shows it's been done. Here's the original thread where it was posted: http://forum.xda-developers.com/showthread.php?t=1664106. Was able to get WiFi calling on ICS even though there was never a stock ICS ROM for the G2.
So it might be in the realm of possibilities. I do know that the G2 had a lot more dev activity though.
Click to expand...
Click to collapse
Ok.
It's possible.
However, T-Mo pushes out plenty of updates to their Wi-Fi calling that aren't aimed at improving service; they are released to break custom implementations. The difficulty of porting and maintaining Wi-Fi calling is the reason it probably won't happen on this device.
Regardless, there is no 100% perfect custom rom that will shower you with perfect mana from the heavens above and make poo smell like cinnamon rolls.
Every rom (including stock TouchWiz) is a tradeoff. That's just life.
ameer1234567890 said:
Try CM10.2 which is the most stable custom ROM for this device. Also, you can try CM11 which is pretty stable too.
Click to expand...
Click to collapse
+1 CM10.2 stable is working great
jgummeson said:
I'm coming from the HTC G2 and for awhile I had a custom ROM with WiFi calling. Technically I think I had to install it as an addon after I flashed the ROM but it shows it's been done. Here's the original thread where it was posted: http://forum.xda-developers.com/showthread.php?t=1664106. Was able to get WiFi calling on ICS even though there was never a stock ICS ROM for the G2.
So it might be in the realm of possibilities. I do know that the G2 had a lot more dev activity though.
Click to expand...
Click to collapse
I believe this is the old implementation of Wifi calling, which T-Mobile changed mid 2012, before the release of the Relay. There's a nearly $1500 bounty posted somewhere for someone to get the new implementation working for modern phones on AOSP based images.
Magamo said:
I believe this is the old implementation of Wifi calling, which T-Mobile changed mid 2012, before the release of the Relay. There's a nearly $1500 bounty posted somewhere for someone to get the new implementation working for modern phones on AOSP based images.
Click to expand...
Click to collapse
Yeah you're right, it was the old implementation. Realized you specified the "new implementation" after I posted.
I'm using KatKiss in a 3G model, and everything is fine.. but now i need to use 3G SIM connector, and this rom doesn't seems to support it. There are other options, and for what i could understand, the best rooms to fully support 3G models are based on 4.04 (?right?)... I need help deciding the best room, i could test every one of them, but... i have to leave country in about a few days, so if someone could point one out, it would make everything simpler. Thanks in advance!
I am using Revolver 4.02.01 (IC421G - 3G version) since a long time. Its the best rom for me, because there is no need to use PPP-Widget.
everything is working fine and stable. Be carefull by flashing a Rom on the TF101G. When you are not able to read the SD-Card while flashing,
you got a big Problem!
Hey there!
I'm using the nightly release of CyanogenMod 11, the unified Motorola 8960 build on the XT926 (Verizon) variation of the phone.
My problem is that the WiFi range is much less than that of the stock build. While using CM11, I will get disconnected at some places in my house that I was getting a good connection for at stock.
I've tried restoring back to my stock firmware backup to confirm that it still works, and there is no issue there. I only have a problem with range using CM11.
I do get a fantastic connection elsewhere, closer to the router though.
If anyone has any suggestions, I'd be grateful for them.
I'm thinking perhaps I could take the wireless drivers from the stock firmware and replace them with CM is using? I looked a bit for how to do that, but I had no luck there, and managed to break wifi completely! :laugh: (I made a backup first at least.) But if someone knows how to do it, that'd be great.
Thanks!
Edit: Both 2.4 and 5 GHz bands are working excellently as of Nightly 7-31. Problem solved. Thanks everyone!
I'm seeing the same thing here, for what it's worth.
I don't think it's the drivers, though. There are a lot of configuration files that fine-tune WiFi, and I bet they haven't been optimized yet.
These are nightly builds, after all.
If I hadn't been having so much trouble with stock KitKat, I never would have flashed CM11. Overall, I'm much happier now.
You can go edit the xml files, or just wait for the next milestone, it should be better.
Or do what I do: keep flashing the nightlies, roll those dice again!
Android Tweaker 2 in the Play store, might be helpful.
Good luck!
docwebhead said:
I'm seeing the same thing here, for what it's worth.
I don't think it's the drivers, though. There are a lot of configuration files that fine-tune WiFi, and I bet they haven't been optimized yet.
These are nightly builds, after all.
If I hadn't been having so much trouble with stock KitKat, I never would have flashed CM11. Overall, I'm much happier now.
You can go edit the xml files, or just wait for the next milestone, it should be better.
Or do what I do: keep flashing the nightlies, roll those dice again!
Android Tweaker 2 in the Play store, might be helpful.
Good luck!
Click to expand...
Click to collapse
I like CM11 quite a lot so far, and like you would rather use it over the stock ROM. But if I cannot connect at all places in the house, I'll have no choice but to go back for a while.
I'll definitely give that app a try and see what I can get out of it. Thanks!
This is a known problem in CM11. Hopefully it's being worked on.
I definitely have this problem, but more at work than at home. It works fine at home, even though the signal is weaker in some spots than it was under JB (even under stock KK, the WiFi signal is weaker than it was under JB).
Like others have said, I'm sure the devs will work on this. I keep flashing nightlies myself, and reading the change log to see if it addresses anything with the WiFi signal. I'm sure it will eventually get fixed.
Some news for the patient
By all means, get the 7-31 Nightly!
It has almost completely fixed the wifi issues for me. I hope it does the same for you!
I flashed cm-11-20140731-NIGHTLY-moto_msm8960.zip which I found at get.cm/get/inm
(Sorry, can't post a proper link...)
And most everything Just Works(tm).
Hope it works for you, too!
Good luck!
docwebhead said:
By all means, get the 7-31 Nightly!
It has almost completely fixed the wifi issues for me. I hope it does the same for you!
I flashed cm-11-20140731-NIGHTLY-moto_msm8960.zip which I found at get.cm/get/inm
(Sorry, can't post a proper link...)
And most everything Just Works(tm).
Hope it works for you, too!
Good luck!
Click to expand...
Click to collapse
I agree. The WiFi strength at work seems so much better under the 7-31 nightly. No going back to stock now.
The Gummy Milestone 3 nightlies have had solid WiFi for a while now.
docwebhead said:
By all means, get the 7-31 Nightly!
It has almost completely fixed the wifi issues for me. I hope it does the same for you!
I flashed cm-11-20140731-NIGHTLY-moto_msm8960.zip which I found at get.cm/get/inm
(Sorry, can't post a proper link...)
And most everything Just Works(tm).
Hope it works for you, too!
Good luck!
Click to expand...
Click to collapse
I'm glad someone replied to this thread, because I kept forgetting to come back and update it.
I noticed that around Nightly 7-26 or 7-27, the 5 Ghz N became stable and had excellent range. This is fantastic for me, because I have a 5 Ghz dual-band N router. And while this phone is advertised as dual-band N, it's never worked with the stock firmware. At least for me. N in 2.4 Ghz worked under stock, but that's not what I wanted. So I've been happily using CM11 since I found that was now working.
And as you and others have mentioned, 7-31 seems to have the 2.4 Ghz G network working smoothly now. (I swear it feels slightly slower than stock was, but it's probably my imagination after being used to the performance I've been getting on N.)