yashsingh1/xdaforums huggingface dataset:
[Epic 4G General] gTen:
Right now the only way to do that is use wifi for data or 4g for data..

if they upgrade to SVDO in the future you can do both as mentioned above...
[Epic 4G General] churro7:
no i meant when i am on 1x and actively surfing no calls coming ie i miss calls. is there a way to prioritize calls overriding an activate data stream?
[Epic 4G General] APOLAUF:
No. There is no way to change this. That's the nature of the current 1xRTT implementation. I think this is done at the tower, and not on the phone.
[Epic 4G General] lazydazed:
I miss calls a lot when I have bluetooth on and listen to pandora/slacker.. I think the phone gets confused, too many radios active.
[Epic 4G General] musclehead84:
How do you all.even know you are in the 1xrtt network and.not 3g?

Sent from my Evo Killer!!!
[Epic 4G General] Overstew:
I've gotten many calls while surfing the web, even text messages come in. They did recently just upgrade my service at my house, though. (If it is a tower possibility.)
[Epic 4G General] digiblur:
Either a theme with the icons fixed or the mobile signal widget.
[G2 and Desire Z Q&A, Help & Troubleshooting] andersonjacob54:
My SetCPU has only about 3-4 different frequency options between 806Mhz and 245 MHz. Is there any way to increase the number of options between these two frequencies?
[G2 and Desire Z Q&A, Help & Troubleshooting] jojo_16:
U have to root your phone and flash some ROMs depending on which type of rom do you like, it comes with kernels for overclocking or you can flash one if you want to. Rooted stock rom doesn't have any compatible kernels it breaks some stuff so you really need to use a different rom..

Fly like a G2
[G2 and Desire Z Q&A, Help & Troubleshooting] martonikaj:
Well if he's using SetCPU then he's already rooted, so he's got that covered.

OP as jojo stated, you need a custom kernel to allow overclocking. A lot of people seem to be fond of Pershoot's OC kernels, but I personally just use the one thats included with CM6 and now CM7. It allows an overclock up to 1.5ghz.
[G2 and Desire Z Q&A, Help & Troubleshooting] KCRic:
I think he's wanting to know how to add more underclock frequencies. It can be done but you have to decompile the kernel in order to do it and also have decent knowledge of voltage tables (since the purpose of underclocking is to save battery power you have to uv also). Probably well beyond most peoples comfort level however, if the op still wants to attempt it are numerous threads with info - just search for something like 'creating a custom kernel' or 'make a kernal'. One of them is located in the G2 development forum.
[G2 and Desire Z Q&A, Help & Troubleshooting] andersonjacob54:
Oh ok thanks guys. Yeah, I have Pershoot's kernel so that is not a problem. I was trying to include more underclock frequencies, but if that means editing or creating my own kernel then forget it lol, I'm no expert on that.
[G2 and Desire Z Q&A, Help & Troubleshooting] jojo_16:
There's a turbo ROM that can deep fry your G2 to 1.8ghz, and it has a lot more frequencies below 806.

Fly like a G2
[HD2 Android Q&A, Help & Troubleshooting and Genera] weezybaby307:
Hey there

I need your help guys

Everytime i restart my hd2 all settings are lost and many apps wont work anymore.

I use the magldr 1.13 , this nand build HD2_Core_Droid_Desire_HD_V1.2.

After every restart i have to restore all apps and settings with titanium Backup, it sucks.

Has anyone else the same problem or am i the only one.

Im thankful for every help and solution.

If you need any other informations say it.

Thanks guys :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] weezybaby307:
No One any idea or solution ?
[HD2 Android Q&A, Help & Troubleshooting and Genera] wrecless:
I am currently using that rom and I have none of those problems. I think you need to fresh install and make sure you follow all of the instructions from the download DO EXACTLY AS IT SAYS you cant go wrong. You must have missed a step like sd card partition or something
[HD2 Android Q&A, Help & Troubleshooting and Genera] weezybaby307:
Ok i will try it.

But ive followed all instructions.

Thank-you for answering.
[HD2 Android Q&A, Help & Troubleshooting and Genera] weezybaby307:
I did a hot restart and a few hours later i pulled my bat off because the phones wiped.

And now is everything ok i dont understand it xD but its fine :)

A few apps disappeared but Thats not necessary.
[Touch Pro2, Tilt 2 Android General] muziling:
create an apn, defaut mmc=310, mnc=995, if I change this values, apn can not be saved success, and log output:

E/TelephonyProvider( 4581): Failed setting numeric '310995' to the current operator
[Touch Pro2, Tilt 2 Android General] muziling:
This is because libhtcgeneric-ril.so code has line:

asprintf(&imsi, "310995000000000"); //Fake opID
[Xoom General] harajuka:
Does anyone know if xoom/honeycomb will support live wallpaper? I haven't seen any honeycomb tablets with a live wallpaper yet..
[Xoom General] Sirchuk:
New ones probably bed to be made or scaled up.
[Xoom General] Old MuckenMire:
I actually saw a hands on that had a live wallpaper running. It was a subtle one, not a whole lot going on, but the background was moving. The user actually selected wallpapers and you could see the live wallpaper option. It's going to come with it's own set of live wallpapers, just like all Android devices do.
[Xoom General] Gamul1:
I am really hoping to add a live wallpaper like I have on my Droid Incrediable - the Water wallpaper where the autumn leaves float along and if you tap it the water ripples.

I entertain easily....
[Galaxy Tab Accessories] geek_riot:
Hi I have a bluetooth keyboard \ mouse combo that works great except that when I type the on screen keyboard pops up as well. I use swiftkey, and so I can swipe down to hide the keyboard, but I would rather have the keyboard not pop up at all when using the bluetooth keyboard. Anyone know how I might accomplish this? Oh yeah, it does it regardless of what keyboard is an using.
[Galaxy Tab Accessories] Azhad:
As esc is the back button, you can press it to hide the keyboard, faster then swiping it down

Sent from my GT-P1000
[Galaxy Tab Accessories] ayman07:
There's an app that is called blueinput that is suppose to give much more functionality to a connected Bluetooth keyboard including a way to hide the on-screen keyboard. Unfortunately I couldn't get it to work. try it. Its in the market.

From the Tab.

www.twitter.com/ayman07
[Galaxy Tab Accessories] lambstone:
Or you could install wifikeyboard from the market. This ime would not block
[Galaxy Tab Accessories] dudyk:
I just patched AnySoftKeyboard to automatically hide on hardware input... when it's integrated, it could be a good option.
[XPERIA X2 General] legacygt777:
what are the 1st three things i need to do to make my new x2 work at its best?
[XPERIA X2 General] dolle82:
Update to MR2.. Then remove panells just not the spb.. then search this forum..
[XPERIA X2 General] indycar:
update to MR2 than customly install needed cabs (find a topic on here)

do the little registry edits download latest spb shell

overclock to 1056mhz - optional
[Droid Eris Android Development] Nomad145:
Here's what Cyanogen said on the Official CyanogenMod Forums.

http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right

With this said, why don't we jump on the bandwagon and just join the CM team? Why don't we make this thing official (if we haven't tried already)? Just a thought, so don't kill me with your opinions. :P The Devs here are freakin' legit here and I'd like to see 'em do some of the work on the CM Team.
[Droid Eris Android Development] amfetamine:
I trust the devs I download from because I follow their work. I don't need it to be "official". Besides, I like the personal touch and one-on-one support I get right here on the xda eris forum. And there's variety.

We could debate the politics of branding and what is CM and what is not CM. But the devs here disclose their sources, changes, known issues and brand their roms as uniquely their own while providing the support and updates. I don't think there's any confusion as to what is 'official' and what is not as the Android Police article referenced in CM's statement implies.
[Droid Eris Android Development] mjb413:
+1. The devs here are excellent, and the devs that base there ROMs on CM list them as "based" on CM not the official CM ROM. I'm not aware of any confusion that this has caused. I'm also not sure what creative constraints would be put on our devs if they went CM. I like the way they individualize the roms for thier personalities and their audiences. I also am not sure what benefit would come with being an "official" CM rom. Just my 2 cents.
[Droid Eris Android Development] Nomad145:
Don't get me wrong, I'm not discrediting the Developers that cook these ROM by ANY MEANS whatsoever. They do incredible work with what they push, but here's what I'm saying. The CM ROMS are based off of Official CM Source Code, yes, but I think we'd be making it way easier on ourselves and the developers if we were an actual part of CyanogenMod. If we were a part of CM, then we'd get the CM ROMS as perfect as they can get and THEN the developers can add their own customization to a ROM based off of the Eris Release of CyanogenMod. They all are already doing the work that it would take to actually /BE/ a part of the CyanogenMod team, so why not get on with CyanogenMod so we can be official, and THEN the devs can customize and tweak ROMS they way they see fit?

Once again, absolutely NO discredit to the developers here, and I understand what it takes to keep these ROMS current and I am very appreciative of their work.
[Droid Eris Android Development] gnarlyc:
The CM ROMs that we have are either built from CM source or ported from the Hero builds already. I'm not really sure what this would give us other than maybe a "go team go" feeling and maybe a little more help than we already get. But the Eris and CDMA Hero are so similar, that doesn't matter much in my opinion as long as any Hero issues get worked out.

The CM buildbots are just building from source and posting the results, much like you would get if you ran EasyDev or did it manually. Now, there's a lot of work going on before that with the code, of course. But... That's what we use too.

I'm not against this at all. It just means that someone will have to 1) want to do it 2) have the time 3) convince Team Douche to let them in. I seem to remember that someone asked early on and the response was that we had to send them an Eris. This might have changed.

This comes up every so often. I guess one of us can find out what we would need to do at least...
[Droid Eris Android Development] Conap:
Nothing would really change for the end user if we became official cm at this point. Basically one of the devs here that builds from source would submit their vendor tree to the cm source and they would be responsible for maintaining it just like we do now. The only real difference would be that it would get built by the cm build bot and nightly's would be released. I tweeted to cyanogen about getting my 2.2 tree in there along time ago when 2.2 was new but either I did it wrong(not a twitter person lol) or it just got lost in the many many tweets that go through cyanogens account. I never really pushed the issue more because of the extra time it would take me personally and it was just easier to work on my own schedule.

The only added benefit would be that maybe if there was an issue we could not fix then the cm team would take an extra look at our specific phone to help out but really since our phone is so close to the hero and it has official support they sort of fix most of our bugs anyway. I've personally always tried to give the cm team all the credit they deserve(which is alot) and I think the other dev's do the same.
[Droid Eris Android Development] KarateExplosion6:
Here's what Cyanogen posted up to www.cyanogenmod.com a week or so again. It looks like we'd need an interested dev here to stop by #cyanogenmod-dev on Freenode to start the process.

I think (and I use xtrSENSE, so I could be wrong) that a lot of people would like and "official" CM port for the Eris, just so they'd have "peace of mind" knowing they've got something "official."

And again, as we've seen mentioned in this post, it couldn't hurt to ask. Provided Team Douche doesn't actually want an Eris, we only stand to gain extra help on our ports.
[Droid Eris Android Development] hallstevenson:
Oh no, does this mean we're all running unofficial CM ROMs ? :eek: :eek:

Wait, everything is working fine though... :confused: Official, unofficial, pffft
[Droid Eris Android Development] roirraW "edor" ehT:
+1 10 char......
[Droid Eris Android Development] refthemc:
A dev would have to maintain the device and be committed to building it up, like Darchstar was (is?) for the Hero CDMA. It really all depends on the Dev/Devs for the device, for example I've seen Cyanogen say in his twitter that he would also like to see the Dream/Saphhire continue to be developed for but no one has stepped up to maintain it. I can also only imagine that there are some qualifications for someone to maintain a device. Here is a list of the current maintainers for the devices

https://github.com/cvpcs/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
[Droid Eris Android Development] Nomad145:
Yeah, I can understand that. That's all I was saying, though. If they were doing all of the same work anyway I just thought it would be nice to have. I also didn't know if anyone had pursued this in the past, but seeing as how Conap had already tried I think I'm good with that. I also have no problems running the unofficial ROMs, just so you know. :) Thanks, guys!
[Droid Eris Android Development] Hungry Man:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
[Droid Eris Android Development] tazzpatriot:
the way i do it is best for me,,and seems to be going fine,,, the cm7 ports have been alot better then the froyo ,, and alot faster ,, look how long it took the froyo camera to work,, gb the camera works outta the box,,:D
[Droid Eris Android Development] gnarlyc:
There is more than one definition of porting that people are using around here.

1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)

2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)

Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.

The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
[Droid Eris Android Development] tazzpatriot:
I thought it was a girl :confused:
[Droid Eris Android Development] refthemc:
Its a dude.

http://www.youtube.com/watch?v=3zb64y6Nvs0
[Droid Eris Android Development] tazzpatriot:
nope still a girl

http://www.youtube.com/watch?v=vwIa2S0YQs4
[Droid Eris Android Development] KarateExplosion6:
FYI: http://twitter.com/cyanogen/status/45246447385452544
[Droid Eris Android Development] wildstang83:
I think OUR devs are doing just fine. Why change now?

wildstang83
[Droid Eris Android Development] KarateExplosion6:
Our devs are doing more than just fine, especially considering the amount of development we STILL have going on even though the Eris was a short-lived device that was EOL'd after like 8 months, was mid-range compared to the original Droid, and is a pretty niche device being MDPI on Verizon...

Why change now? That's a good question and I don't have a great answer. Like some have said on this post, maybe we'll get more support with bugs, etc. Additionally, a lot of the users here on XDA are looking for consistency. Since many who read and post here lack the skill set to do any meaningful ROM development themselves, they rely on the kindness of willing devs. However, devs will often add their own "personal touches" to their ROMs, which is great and well within their right to do. Having said that, many users are just looking to for something where they know, "Oh OK, so this is the base CM ROM that's officially distributed."

Personally, I don't care whether we have an "official" CM build or not for the Eris. I'm pretty reserved when it comes to ROMs for everyday use and am still using xtrSENSE as my default. The only reason I posted up cyanogen's recent tweet was to show that cyanogen himself is well-aware of the Eris development, is personally following the Eris ports, and is open to a partnership. My hope is that, by bridging communication, I am doing my part in helping to expose any possible mutual benefit (Eris XDA devs, ROM end-users, and Team Douche at CM) that could be gained by considering an "official" build. Ultimately, I understand that this is a decision that can only be made by the devs and also, not fulling understanding ROM development or having the skill set myself, I believe they are in the best position to make that decision. Like I said, I'm merely acting as a messenger, bringing this communication to light on our forum.
[Droid Eris Android Development] gnarlyc:
Hi, my name is gnarlyc. My specialty is cameras. :)

In case any devs didn't know this already, here are the requirements per folks in the cyanogen-dev IRC channel.

----------------------

1) working repo preferably on github

2) 100% device hardware support (no major features missing/broken)

3) your time commitment

Once its 'official' it is expected that it will be maintained (bar any OS updates that completely disallow it). Other than that, its fairly simple to get approved and merged into official status.

-----------------------

I do not have the time to fully commit to something like this. If I did, I would be making ROMs right now. It's certainly something that I enjoy doing. I'll be glad to help as much as I can though, if someone(s) would like to go in together. Keep in mind a few things though...

1) There's a lot going on with CM other than swapping files and such. They dig into Java and C code daily to fix things.

2) We would be on their schedule. This is probably not that big of a deal. I don't think they start jumping down people's throats if something isn't getting done right away. They are volunteers too, after all.

I feel like the main reason that we haven't gone this route yet is just not having the devs who have the time or want to commit. It's nothing more than that, really. We all have lives. We all have different skillsets and interests. That's why I'm offering to help. Other devices have multiple maintainers, so I don't see why we couldn't also. I can't go it alone though. Not now anyway. I'm already making little progress on the kernel due to lack of time.
[Droid Eris Android Development] gersto:
I also keep hoping for an official cyanogenmod for the Eris. Its true we have some great devs here working on a device Verizon and HTC have all but forgotten. I think also though that having an official port by CM may prolong the developement once many devs here move on. Although that's not necessarily guaranteed as stated earlier.

I for one am still blown away by worksheds work on the CM7 port for the Eris. As much as I loved xtrROM, this may now become my daily driver. Still trying to see how battery life is in comparison.
[Droid Eris Android Development] ngc604:
I completely understand why some would want official cm7 support. But if we got that it would be a product of either workshed, tazz, and kaos or a combo off all of them plus more. That is pretty much what our roms are anyway. a collaboration with extras from what the dev wants in there and some just pure. I thought it was said that we have 5 or 6 pure cm roms on here. I am willing to bet that once cm7 is completely stable then conap will probably make a celb for it(just speculating here). I think the people who want cm official are just looking for the name. Nothing is in the name. Look at our devices. I have yet to run into anyone IRL that knows about the eris. I blew a verizon techs mind when the dumb ass told me the eris could never run 2.3 and i handed him my eris. He was speechless.

I personally think this is kind of a slap in the face of the devs here. I would be insulted if i was a dev. Make me think people would use my rom if it had an official cm status. Even though it could possibly be the same damn thing.

thank you devs for all your hard work.

sorry for the rant. just my .02
[Droid Eris Android Development] workshed:
working on this now... since I believe the Eris should definitely be Officially supported by CM... I will be submitting my vendor tree to them tonight.

be patient, this will happen soon.

why the change of heart you ask? well, simply because I really didn't understand how many users wished for this to be true... so, I will do my best to make it so! :D
[Droid Eris Android Development] api1996:
That's great!
[Droid Eris Android Development] Stonent:
I feel we're duplicating efforts a lot. Since the CDMA hero is in cyanogen and it is 90% the same phone as the eris.

Same CPU

Same Video

Same radio

Probably same wifi and camera

The main difference is the HW buttons and the Heroc lacks the proximity detector.

If we could just keep the eris as a sub branch of heroc, it would make it easier for Workshed and the others who regularly work on Eris stuff.

I'd like to see someone who has a phone to spare to leave Amon RA on their phone and flash in a Heroc kernel and if it still boots, try a heroc rom and see what happens.
[Droid Eris Android Development] tazzpatriot:
thats what i use :) due to my condition it just makes it easier
[Droid Eris Android Development] roirraW "edor" ehT:
Wow. Everyone and you yourself have sold me on the value of the officialdom of CM for Eris. My take on this is that if you, Tazz, Kaos, and EVERYONE can already make CM ROMs as good as you all do already, I can only imagine how much even better it can be.

THANK YOU!
[Droid Eris Android Development] Captainkrtek:
Glad to see someone is doing this, I know the heroc maintainer very well so if you have any problems resolving issues I can get him in contact with you :) Cheers!
[Droid Eris Android Development] agentlotek:
Exciting news!
[Droid Eris Android Development] KarateExplosion6:
Quoted from Shed's Twitter...
[Droid Eris Android Development] api1996:
How is everything going with submitting to cyanogenmod? When will it be accepted?
[Droid Eris Android Development] workshed:
Just waiting on cm to make a device repo for it :D

Oblivion grabbed & compiled my tree, he had no issues and actually commented on how much faster the phone felt to him (his eris was on stock), said everything was working great, then told me they were looking at getting a device repo up for it some time soon. So, I'm just waiting to hear back like everyone else.

I'll make sure to post a update as soon as it's Officially Official ;)
[Droid Eris Android Development] wildstang83:
Shed you deserve this brother. I really hope they sign you on.

Powered By: GSB CM7 2.1
[Droid Eris Android Development] amfetamine:
In case you didn't feel like showing up:

We're in open!!!

http://review.cyanogenmod.com/#change,3911

Change Iedee7e53: Adding product for desirec