Related
The reason I ask is not at all to be critical of the development going on with Hero, on the contrary, I think it's going very well. However, today is my last day to return the G1 I got 14 days ago. I love Hero and want to use it on a device with a hardware keyboard. The G1 is the only option for that, but I use bluetooth every day in my car. It's a must.
So, I forward the question, are you guys making progress? Can we count on it getting done or should I take this phone back to t-mobile today?
I'm quite confident for the LEDs. The Hero builds are not such a radical departure that we've all been left stranded in the atlantic, so to speak. When it boils down to it, they're still just Android-1.5, with some extra HTC glue on the top.
However, if you're in doubt, why not return it and get the Hero (when it's released)? HTC's software keyboard is easily the best I've used, so the loss of a hardware one wouldn't sting so much. Sure, you'd have to wait for root, but at least you've have a no-nonsense Rosie.
Magic 8 Ball says: "maybe"
in all honesty no one even knows for sure if Hero is coming to tmo. That might be a factor as well. Really though it's still android..and the g1 is a great phone..we don't know anything about the hero phone from a reliability/battery life/heat standpoint yet. It could prove to be the next iphone 3gs.
Keeping it
Ok guys, I'm keeping the phone. That means I got 2 years of Android goodness ahead of me on this G1. Keep up the awesome work Hero guys, and please get bluetooth running. The rom is fast enough now, and bluetooth's the only thing keeping me from jumping over.
Thanks for the help.
afflaq said:
It could prove to be the next iphone 3gs.
Click to expand...
Click to collapse
I love my Dream but that's a big no-niner-niner.
Wii60 said:
Ok guys, I'm keeping the phone. That means I got 2 years of Android goodness ahead of me on this G1. Keep up the awesome work Hero guys, and please get bluetooth running. The rom is fast enough now, and bluetooth's the only thing keeping me from jumping over.
Thanks for the help.
Click to expand...
Click to collapse
Having gotten bluetooth 98% working under Hero rom I'm pretty confident I'll have a solution soon. I have a feeling that with LED's non-functional and tying up the I2C bus with requests to turn on/off the leds which end up failing, this is causing bluetooth to not be able to disable the uart clock, which coincidentally has to be done over the I2C bus. I know, it sounds like a foreign language just be rest assured a fix for both "SHOULD" be coming soon.
Any news?
15 days passed... got any more progress on bluetooth and leds? Please say yes
Is there any workaround?
josevtome said:
15 days passed... got any more progress on bluetooth and leds? Please say yes
Is there any workaround?
Click to expand...
Click to collapse
be patient. why not downgrade ur phone to a rotted cupcake if bluetooth is soo important. hero is nice on the eyes..but in your case it seems like you need function.
cyanogen is a solution.works well.
Right now, I'm using a Rogers dream firmware, and it works really nice. It has about 80% of Hero (mostly HTC Framework, HTC boot animation/sound, and several apps such as the HTC Music app, and the Hero Java JBED (loving it, lots faster than the Netmite J2ME) just without the Rosie/Sense/TouchFLO (yet...), and its associated mods), and 100% of the G1/Dream compatibility (LED's, WiFi, Bluetooth, Audio, etc.)
And there are Hero themes for the Rogers Dream firmware that aren't unlike those of 'lite' Hero builds (without any Sense). Twidroid, Twidgit, and a weather/clock widget would make it indistinguishable in function, for the most part, from a real Hero.
Though I am hopeful for development on the bluetooth issue, and there's a topic (http://forum.xda-developers.com/showthread.php?t=527027) that seems to be making progress on this issue, I can't use a Hero ROM until the bluetooth is functional, as I use my G1 as my main music player, and I don't have a wired pair of headphones to use with them (some kid stole them from me, including the adapter). I do have an iPod bluetooth adapter, but since my iPod 5G, with custom themed Apple OS, Rockbox and Linux, crashed (unsurprisingly), it's not of much use to me currently.
TylTru said:
Right now, I'm using a Rogers dream firmware, and it works really nice. It has about 80% of Hero (mostly HTC Framework, HTC boot animation/sound, and several apps such as the HTC Music app, and the Hero Java JBED (loving it, lots faster than the Netmite J2ME) just without the Rosie/Sense/TouchFLO (yet...), and its associated mods), and 100% of the G1/Dream compatibility (LED's, WiFi, Bluetooth, Audio, etc.)
And there are Hero themes for the Rogers Dream firmware that aren't unlike those of 'lite' Hero builds (without any Sense). Twidroid, Twidgit, and a weather/clock widget would make it indistinguishable in function, for the most part, from a real Hero.
Though I am hopeful for development on the bluetooth issue, and there's a topic (http://forum.xda-developers.com/showthread.php?t=527027) that seems to be making progress on this issue, I can't use a Hero ROM until the bluetooth is functional, as I use my G1 as my main music player, and I don't have a wired pair of headphones to use with them (some kid stole them from me, including the adapter). I do have an iPod bluetooth adapter, but since my iPod 5G, with custom themed Apple OS, Rockbox and Linux, crashed (unsurprisingly), it's not of much use to me currently.
Click to expand...
Click to collapse
are you using the RogHero build? i forget the dev... ah just checked it's Maxisma. hopefully the hero stuff is done soon with BT, cuz i know LEDs are working on some builds now because i really wanna show my dad (who is so not a techie person) that i can run something besides the Dream stuff on my G1 lol. good luck to all those trying to port the Hero ROM to the Dream...
I think I'm using a soulife build, as my /system/build.prop has:
ro.build.display.id=CUPCAKE.eng.Soulife.20090522.075548
I forgot exactly, as I usually keep my update.zip's on the computer except for a couple important ones.
I am currently having ongoing arguments with T-Mobile about how the GPS in the SGS is flawed no matter what they do it for things like navigation, especially when compared to other phones.
I am very close to been able to swap it for another phone, but I want to bring it right back so they can't tell i've had custom firmware on.
If someone can help I'd be very grateful.
Many thanks.
I ran into this article yesterday, How to Flash CyanogenMod 7 ROM Samsung Captivate AT&T, and felt it was about time to learn about this. Plenty of you have already ROOTED your phones, and know from experience, what to do. But, I don't. Right now, I'm stuck with the options of accepting things don't work right, because of AT'T's unwillingness, or inabilility, to correct the issues I have, or reinsiall new, and lose all I've put on, or send back to Samsung for repair, and have them lose all I have on it, or try Rooting and adding a ROM, that may solve my issues. But to do that, I need a little help in understanding it.
First, if I try and run a program, like CyanogenMod 7, and it doesn't work correctly, snd screws up my phone, is there a way I can reinstall Android, and start over, or is that the proverbial kiss of death for my Captivate, and I'm stuck with it like that?
Second, is this the right ROM to try? AT&T can't fix my BLOCKS, of UNKNOWN APPS. The Settings change is easy, you click on activating Unknown, in Application settings..., unless you have no UNKNOWN, to choose. Also, in MMS settings, AT&T shows in a tutorial, that you have the option, of activating Delivery Report and Read Report. It shows this as plain as day, on that tutorial for the Captivate, yet mine, has NEITHER OF THOSE OPTIONS. Also, to TURN ON EDGE, the setting is missing, so I can't activate EDGE, which I guess is no big thing, since the towers AT&T has for us to connect with, THAT ARE 2G, are in such poor condition, no one can connect to them. Thank you, WIFI, for helping me get, ONLINE. Will this, or other ROM's, solve this for me?
If there are any suggestions of how to do this, and what to use, I'd appreciate hearing it from you. Again, I thank any effort, to help me.
1.cm 7 would not be the best rom to flash for your first time.
2. All roms are android, you are running at&t/samsung version of an android rom...
3. Yes you can get back to your stock rom if you don't like/something goes wrong (other than a bad bootloader flash)
4.all custom roms have all the blocking done by at&t removed so switching to 2g(edge) is possible and also faster 3g speeds known as hspa. And unknown sources is in the settings so you can install apps from outside the market.
5.the threads at the top of every section with a little thumb tacks are called stickies, give those a read through.
Like he said above. If you want the pretty much stock experience that your used to but want it fixed then I would suggest starting off with Cognition 4.4 or whatever it is now.
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
From newbie to a newbie, I took the advice of others and read threads for atleast a month before I flashed my first rom. My choice was Andromeda3, It has a written tutorial and a video on how to from start to finish. From what tools or apps you will need and how to use them , I watched that atleast 6 times and also while I was flashing the kernel and the rom. It may have been overkill but my flash was perfect and I'm real happy with my phone now. You may not go with the same rom I did but do your self a favor and do what I did to prepare for your first flash.
Having serious troubles with the GPS (I think ever since I upgraded to KitKat). I've tried a couple of ROMs and went back to the stock rooted one found here. I will get a fix at times but it will be lost within a minute or so and makes things very frustrating.
What's the best way to troubleshoot this? I've tried Chartcross GPS test, but it doesn't fix anything. Any help would be really appreciated.
Anybody?
scopefield said:
Having serious troubles with the GPS (I think ever since I upgraded to KitKat). I've tried a couple of ROMs and went back to the stock rooted one found here. I will get a fix at times but it will be lost within a minute or so and makes things very frustrating.
What's the best way to troubleshoot this? I've tried Chartcross GPS test, but it doesn't fix anything. Any help would be really appreciated.
Click to expand...
Click to collapse
If you google your question you will find loads of the same exact issue. I am also having the same exact issue, it only kind of works on stock rom with no root. But even then not for very long. Samsung decided to put garbage gps radio's in our phones so gps is pretty much non existent on the Note 3. I'm on my 4th phone from ATT. Not only does the GPS suck, the connection losses are pretty unbearable at times and have actually costed me customers. And to think I traded my S5 for this POS....really frustrating.
TLDR: Someone at Samsung needs punched in the face, twice.
Djspinister said:
If you google your question you will find loads of the same exact issue. I am also having the same exact issue, it only kind of works on stock rom with no root. But even then not for very long. Samsung decided to put garbage gps radio's in our phones so gps is pretty much non existent on the Note 3. I'm on my 4th phone from ATT. Not only does the GPS suck, the connection losses are pretty unbearable at times and have actually costed me customers. And to think I traded my S5 for this POS....really frustrating.
TLDR: Someone at Samsung needs punched in the face, twice.
Click to expand...
Click to collapse
Interesting. Mine was working perfectly prior to this whole kitkat ordeal. If I Odin back to stick and reflash to 4.4.2, do you think it will remedy the issue?
That's what i did because I need gps daily, though it still has major issues, I'm literally trying to sell it, my s5 never lost lock, even in my pocket.
Djspinister said:
That's what i did because I need gps daily, though it still has major issues, I'm literally trying to sell it, my s5 never lost lock, even in my pocket.
Click to expand...
Click to collapse
Do you think there's any use in ODIN'ng back to stock and then trying the custom 4.4.2 ROMs or is it not going to work?
Hey guys, I have a vs980 currently experiencing some phantom touch issues & my first instinct was the stock LG bloat could be falsely accusing the hardware of malfunctioning, so i went about seeking custom development with great satisfaction seeing this device wasn't locked into big red's trickery.
Upon scanning across the custom business around here I found most of the same stack references i remember from the Gpad v400, but when i checked my software info it told me I had a BL version 23m?
& I would love any input as to why I can't find anything about this bootstack, as i don't want to go further than current Rooted status without understanding more but the phantom touches are beyond irritating >.<.
any help is greatly appreciated, Happy New Yearz!
Can anybody draw a conclusion from this yet by chance? Really curious as to where this stack came from since im only familiar with 11a 11b 22a 22b, etc, & assumed that they stuck to this fashion of labeling...
Or maybe the only other reference i could use is K0T49L, maybe anybody has an idea? -.-
Got TWRP on with AutoRec, still really weirded out by this baseband version though, just a little background on this specific device it came direct from an employee @ Big Red, as in their own personal phone. So just wondering could I be running the original beta for KK from JB?
Either way will do a full backup with twrp here in the morning & possibly post the boot partition.