yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] thunder9111:
Ok the first time I can connect fine.. but after once the USB is unplugged, I can't load it as diskdrive anymore. It won't show up on my PC. The only way I can fix this is to restart my phone.

does anyone else has this problem? quite annoying to have to restart my phone everytime I want to put files in the phone. and I always make sure sure to click "Eject Android Phone", but it made no difference.
[HTC Desire S] kartikk:
i have used connected my device many time to my pc & never came across this issue...& dont chose any option to eject i just unplug the device

if you were running something when connecting to your pc try exiting everything & you should get the interface to choose usb connection mode
[HTC Desire S] thunder9111:
on the phone the options always pop up, i can click "mount as harddisk", but on the pc there is no reaction and I can't see the drive.

so the drive pops up for you everytime you plug in the USB? weird.. it might be my windows 7 then.. hmm
[HTC Desire S] dam2sekc:
Actually it may be your comp, I had this same issue earlier when i was trying to connect my phone, I just changed usb ports and it pops up fine, so perhaps you could try that????
[Android Software Development] Spz0:
Hey. :)

Im building my own custom ROM, and I am wanting to retain a couple of application settings (launcher settings, and autokiller mem. optimizer settings) by flashing the app data to /data/data/.

I can flash the app data fine in the ROM, but upon first boot of my ROM after flashing, I am getting a UID mismatch in logcat which is causing the OS to overwrite my app data in /data/data/ and replace it with default values due to the uid mismatch.

I've tried the "fix_permissions" script to no avail (Im thinking due to the fact that there hasnt been an initial boot to associate all the apks to their respective app data).

Is there any way I can work around this on first boot?
[Android Software Development] Spz0:
on a side note: We are using clockworkmod recovery 2.5.1.1 (no support for 3x yet) and android 2.2.1, if thats of some help.

thanks in advance. :)
[Vibrant General] xriderx66:
http://www.engadget.com/2011/05/08/nearly-half-a-million-contract-customers-left-t-mobile-in-q1-201/

Will YOU be leaving?
[Vibrant General] fnuffer:
If the merger goes through, then yes. I have been a tmobile customer for 7 years. I have been satisfied with the hardware, the accounts, and even the customer support. Especially the customer support.

AT&T want a stellar company before the SBC buyout, but it became terrible after. I expect the same thing if Tmobile is consumed.

I do not look forward to finding a new carrier.
[Vibrant General] VICosPhi:
I don't think I'll leave TMO unless AT&T acquires it and doesn't let me keep my current plan and pricing. I travel accross USA and do not have a voice coverage problem with Tmobile. Its excellent with few to none dropped calls. But the data sucks, my phone switches to edge 80% of the time as compared to my co workers AT&T and Sprint.

Not to mention I pay less than $160 for 2 lines with unlimited everything.... The next cheapest is sprint @ $210
[Vibrant General] Br1cK'd:
If the buyout goes through, absolutely leaving. I will never be an AT&T customer again, even if it means taking my Vibrant over to Simple Mobile.

Ginger Clones of the World Unite!!! via the XDA App
[Vibrant General] KWKSLVR:
I'll be leaving as well. As far as when, that depends on when the merger goes through and who gets the SGSII. One things for sure, I'll NEVER use AT&T again.
[Vibrant General] oka1:
I agree with most the other comments....... I pay 152 per month for 2 lines unlimited everything......... and I use it............ When and IF ATT does get T-mobile. . . then I will have to find a new carrier, I really like TMO but tempus fugit......

As far as the customer loss I do not see that as a real big issue, if I remember correctly, the average for all the major carriers is between 6-8 million per carrier per year or as it is called in the industry the "churn"

I agree with KWKSLVR it is about who gets the S2
[Vibrant General] Mr. Apocalypse:
It depends on my dad....he pays me and my sister's phone bill cuz we're in college...no matter if we stay or go...i still gotta unlock my Vibrant for another carrier :rolleyes:
[Vibrant General] Bombhash:
If the plans stay the same then ill stay plus some might have better coverage

in areas they never did
[Vibrant General] N8ter:
T-Mobile coverage is terrible Verizon has the iphon now and at&t had some good Android phones.

I'll be leaving.

Also, t-mobile hasn't cared about building out their data network for a long time. Data id more important than voice to me. I use 50 voice minutes a month but 2gb data. I don't mind paying more for a better network...

Sent from my HD7 using Board Express
[Vibrant General] itstheshawnp:
any other provider sounds better then att. i would gladly switch to boost with an unlocked android. or even metropcs has got a few good androids to date. att is making a losing bet unless they all of a sudden change their pricing plans.
[Vibrant General] XPLANE9:
If you knew T-Mobile coverage was bad in your area perhaps you should have started out with a different carrier in the first place. Here in Dallas I get 3G or H almost everywhere.
[Vibrant General] os2baba:
Add me to the list of people who will leave T-Mobile the day AT&T goes through. Keeping my fingers crossed that it doesn't happen.
[Vibrant General] N8ter:
Hi idiot.

I did. No one else had coverage but t-mobile thanks to voice roaming, but at&t put a New 3g tower up so now they have everything. I went from at&t to sprint before t-mobile.

Thanks for using that pea sized brain of yours, though.

At&t... Building out their network.

T-mobile... Dead end.

And traveling with a t-mobile phone is a lesson in frustration compared to at&t other Verizon.

I'm with them cause I live in a rural area and had no choice then.

NOW I do... So ill be leaving.

Don't care where you live and how your signal is, tbh. even at the hspa+ market down the interstate your phone can go from full 3g to edge at any random time.

T-mobile are not defendable, so stop ****ing trying Even with good phones and low prices people are leaving, and for a reason. They aren't spending more just cause they can... There are sizeable cities here that can't get more than 3 bars gprs from t-mobile here, but the other three carriers have full 3g

Thank you.
[Vibrant General] boimarc89:
I've been a T-Mobile customer for almost 5 years. Up until I transferred to the college in this town now, my 3G data service has been great. Im actually so unhappy w/ T-Mobile..Right now i live in Huntsville,TX where I goto college at and T-Mobile is beyond garbage here. Personally, If I'm going to pay the same amount of money as someone who has 3G/4G coverage, i have to have to have the same equal coverage. I'm back and fourth on GPRS and Edge here missing important calls like clockwork. I can get a similar plan with AT&T for the same amount with 4G service here in this town. (Trust me i work for Radioshack and I know all about both companies plans and prices as well as restrictions) When the Samsung Galaxy S2 comes out this summer for AT&T, I'm leaving T-Mobile to give AT&T my money instead. I'm not handing over my whole pay check for a Verizon phone LOL and I'm not going to Sprint with their 3G coverage map looking like a pepperoni pizza LOL

For the most part, T-Mobile has been beyond great as far as customer serviceand pricing, its just that voice and 3G data coverage is, always, and forever will be their weakness and that doesn't work for me.
[General Questions and Answers] acemarko:
after traing to update my pulse mini shows me error and i removed the batery and since than wont power up please help
[Android] JDV28:
hey everyone, I've been with android since release on the g1 and have followed it since. but now I'm tired of being just a user and want to learn how to develope roms. I would rather have some one teach me first hand, but links to some places that helped you would be great too. So again, Im looking for a dev who would want to teach me, if some money is wanted, that's fine. thanks for reading. reply here and/or PM me. I am very serious about learning, I dont just want little tips/tricks or pointers.

Edit: I have a bit of skill in C++ and Java, but nothing too significant. I lost interest in writing programs, same with apps, no interest, everything has been done over and over again.
[Android] stoute:
I have created a site specifically just for this. I have a link in the signature but feel free to just click here @green rom project
[Android] yousif666:
Thanks alot. :D
[Android] rufen:
thank you too
[Android] JDV28:
I didn't find anything there that isn't here on xda.
[Android] aitorTheRed:
Maybe, but for new users in building roms, it's easy if it is gathered in one place, instead of searching all over xda :) that sometimes you can get yourself lost :)
[Android] jbirdvegas:
What ARE you looking for?
[Android] JDV28:
Some sort of a guide to developing roms. even porting. not an "all in one" guide. thats unrealistic and would most likely suck, seeing as its such a broad subject.

that site, is... i dont even know. not to insult you, but i found it to be useless. the single guide you have on there is for setting up the htc kitchen, which i figured out in 5 minutes on my own. I would suggest making a "Guides" section of that site, so it isnt JUST forums, and adding, well, GUIDES. you pointed me there to help me, but there was nothing on the forums even close to helping me.
[Android] jbirdvegas:
What os are you running? Have you succesfully compiled the source yet either aosp or cm?

CyanogenMod's github is a great place to learn repo the source. Read the commits @ github.com/cyanogenmod all commits are commented to make reading changes easier.

Aosp is also on github@ github.com/android building aosp can be more tricky.

Cm is aosp with many custom packages included to see what is and isn't aosp look@ github.com/CyanogenMod/android

default.xml contains references to what packages are cyanogen and what is aosp

Either way you need to start by getting very familiar with

github.com/CyanogenMod/android_vendor_cyanogenmod

Look in the products folder at the .mk files

and how they are invoked by core/Makefile in

github.com/CyanogenMod/android_build

Also pay attention to build/envsetup.sh
[Android] jbirdvegas:
How noob at developing are you?
[Android] JDV28:
your last post was quite helpful. Barely anything at all.
[Android] jbirdvegas:
best bet start by getting the source to compile... sounds simple but can be tricky

most importantly get to know ~/android/system/build

you can't produce a custom rom without understanding when and how everything is compiled
[Android] Slatter39:
Android Kitchen will be your best bet. Very easy to follow. Read the whole post at least twice and you will be good to go. Follow all the links.

This is what i used from the ground up and i have my own rom on my HTC EVO 4G.

http://xdaforums.com/showthread.php?t=633246

http://theunlockr.com/2010/03/26/ho...om-for-android-part-1-setting-up-the-kitchen/

http://theunlockr.com/2010/04/15/ho...m-for-android-part-2-creating-your-first-rom/

Credit goes to dsixda. he created android kitchen. If you like this, please donate to him.

"Dont forget to hit the thanks button if i helped you"
[Android] Macrodroid:
I'm new to the Dev world myself... I've done a lot of reading and research and I've gotten to the point of building and modding Roms to contribute to the community here. I've only done rom's for the Eris, which isn't as complex as some of the other devices, but I'm willing to share my knowledge if you need it.

The basics you will need:

1. Linux (I've tried doing this in windows, not worth the hassle!), either ubuntu or linux mint work well (Mint is a windows "like" os, so it might be easier to start with that).

2. Android SDK Kit (You can google it)

3. APK Manager (If you need to decompile APK's to make changes, this tool makes things a lot easier!)

4. Android Kitchen (A must if you are porting and to keep your Rom's cleaned up!)

5. A working understanding of XML and some java code is extremely helpful!

6. Time and Commitment! Devving, by any standard, is a time consuming process! You can easily make a Rom, but keeping the masses happy requires updates to nightly sources and time to rebuild what you've started!

I've spent so much time updating, compiling, modding and theming that my family voices plenty of complaints! But, the reward of building something that works and seeing others benefit from your creation is well worth the effort! Balancing your time, if you have a family to consider, is key to succeeding with this!

If you'd like more help, send me a PM! I'll work with you as much as I can! :D
[Android] JDV28:
I setup the kitchen, as i previously said, but didnt find any use for it except maybe adding minor features to a completely stock rom. i have linux set up with the SDK. i just dont know where to go from there...even compiling from source
[Android] jbirdvegas:
Read everything here

http://wiki.cyanogenmod.com/index.php?title=Building_from_source
[Android] Macrodroid:
Sent you a PM back, bro.

Having Linux, SDK and the Kitchen setup gets you about 75% of the way there!

The basic steps to compiling from source run through the Terminal in Linux. You will need to pull in the CM repository (the link jbirdvegas posted will give the instructions to do that). Once the repository is setup, you will need to load the proprietary files for the device you're building for in order to sync the correct source. (repo sync -j16 will sync the source and build your folders for compiling). You will need to plug in your phone through USB and extract the proprietaries through ADB. Example, my build location in Linux is "android/system" in that folder there will be a device folder with folders for each device brand and build. My eris is listed in CM as desirec, so my drive folder location is "android/system/devices/htc/desirec". In order to pull my proprietary files, I would have to do the following:

1. In terminal; "cd android/system/devices/htc/desirec" (This puts me in the correct build folder)

2. su (puts terminal in root) - type in password

3. "./adb kill-server" (shuts down adb)

4. "./adb start-server" (starts adb)

5. "exit" (puts you back in standard terminal)

6. "./adb devices" (verify your device shows - if you get ????????, adb did not start right)

7. "./extract-files.sh" (this will extract the proprietary files from your device and place them in the device folder for building)

8. "cd"

9. "cd android/system" (puts you back in the CM build folder)

Once that's done, all you basically need to do after that is:

"source build/envsetup.sh" (Setup source build)

"lunch" (this will give you a list of builds - pick your device)

"make -j# bacon" (# is the number of processors your phone has +1)

The Repo Sync and Make commands will take time, but once you've finished the Make cycle, your Rom (if there were no errors) will be compiled, signed and ready to flash on your device. From there, you can use the kitchen to add "tweaks" to your rom (CM sources are usually pre-setup, but you can still add things like "data/app" access to your Rom).

Hopefully this takes you to the next step. PM me if you run into problems, I'll help you through it.:D
[Android] jbirdvegas:
If you get abd shows your device as ??????????

Google 51-android.rules on how to setup udev
[Android] JDV28:
about 50% of those pages are empty, does it matter what phone i click on for now? nothing shows up for Glacier
[Android] Macrodroid:
jbirdvegas has it right on the adb correction if your device isn't found. I'll look for setting up the rules and post the link a little later.

Glacier doesn't have instructions yet, but there are CM builds for it. If you follow the evo instructions that will get you setup. Just replace supersonic with glacier to get your device established. There wasn't one for the Eris, either, and the EVO instructions are what I used.

Also, if you're building for GB and you're on a 32-bit system, it will tell you you cannot build it. There is a bypass; I'm using a 32-bit system and just removed the "end" statement in the make file. My builds work just fine, so bypassing the environment won't mess up your builds...
[Android] JDV28:
thank you very much, like I said in the pm, not home today so I'll get back to you when I have time to do all of this
[Android] jbirdvegas:
This isn't a cut and paste how to but read the whole page and setting up adb to work with linux's udev will make more sence. If you are learning its better to know why things work then just knowing they work ... that was more wordy than I intended sorry.

http://developer.android.com/guide/developing/device.html
[Android] JDV28:
edit: nvm, ill update once ive finished setting up adb and have compiled source :D
[Android] Nitro_123:
Same here, i really wanted a thead like this
[Android] JDV28:
Well here it is :) Thanks to a few people who have posted in this thread, I have successfully compiled CM from source.
[Android] jbirdvegas:
Time to start forking projects to improve. First fork github.com/android (whenever you fork a project change the corresponding refs in default.xml to your github account) then android_vendor_cyanogen look at the products folder
[Android] JDV28:
explain? 10char
[Android] jbirdvegas:
The android package is a list of what packages to download when you repo sync if you fork the package when you want to use one of your packages then change the package ref to point to your github instead of cyanogenmods

The vendor tree is where you set a lot of settings you will want to change. Also learn how the build system works expecially as it moves through the vendor tree

... ie vendorsetup.sh invokes /products/cyanogen_(yourDevice).mk invokes common.mk .... and so on.

If you want to make a custom rom you need to learn how the system builds itself and it is a complex process.
[Android] jbirdvegas:
I got to thinking when I say fork a project you need a github account to do that. Get used to using github as everything is hosted there.
[Android] JDV28:
I get what your saying, but I need a WAY to learn how it works..going through the guide got me to a good starting point but didn't teach me anything.
[Android] allofusjw:
This is also my major stumbling block in learning how to develop. Its one thing to follow a step by step guide to learn how to compile a rom, yet, its a whole other thing to actually grasp the logic and reasoning behind the processes that need to be performed.

The time it takes to read .mk files and try to follow that maze in order to learn what does what and when and why is beyond what most people can devote. Ideally, there would be a step by step guide *with explanations* to the use of github targeted specifically for android development which covered roms, kernels, recoveries, forking, cherry-picking etc and, most importantly, how to bring everything together to successfully compile your own custom whatever. I think that if such a guide existed/exists(in one place) that could enable a person to start from scratch with a far greater grasp on the whole process and would help in the comprehension of things like .mk files in any other repo.

Once a person can fully comprehend and accomplish this it would help enormously thereafter as you could then focus better on individual components of your build and actually go deeper into the coding side and attempt some true development. Sorry for rambling. If such a singular guide exists I've missed it in my confused search of sites, forums, threads, posts etc. Thanks to the contributors in this thread for taking the time to attempt to help the op. Its always awesome to witness the generosity of the experienced in helping the inexperienced that exists on threads such as this.
[Android] jbirdvegas:
Ok well the biggest question is what do you want to do with your ROM?

in the ~/android/system/vendor/cyanogen/products

Start by looking at the .mk files and how apps are included

PRODUCT_PACKAGES += #used to add packages
PRODUCT_PACKAGE_OVERLAYS += #inherits overlays useful for theming and config.xml for custom app settings
PRODUCT_SPECIFIC_DEFINES += #used for kernel maps specific to devices
PRODUCT_PROPERTY_OVERRIDES += # look for how you can syntax ro.* properties

start by

add packages / remove packages changing properties to your liking.

want to get a more aosp start swapping packages with the aosp but be careful the packages are often interdependent. :p
[Android] JDV28:
What would I add/remove and how? The .mk file for the glacier only has one of the lines you posted above anyways.

and there isnt any properties in those mk files to change.

addition: I want to be able to understand how it generally works and how to optimize for speed, tweak any setting i can think of, etc.

My goal here isnt to be able to build a rom from the ground up,

its to be able to modify/improve other roms and edit them to

my liking. Thats why I'm not particularly interested in the very inner workings.

Does that all make sense or am I just rambling lol
[Android] johnjjschmidt:
It's one thing to be blunt but I'm sure you can find better ways to express yourself and still be direct. I and scratching my head figuring out why you insist on being rude to those who are trying to help you.

Sent from MyGlacier.
[Android] JDV28:
Huh? NO part of that was meant to be rude at all!

I'm very grateful for everything that he specifically has done for me.

I was just expressing my hate for certain things.

I mean, I dont planning on creating the next big rom or competing with someone,

I just want to know enough where I can customize a rom

that i like and make it even better

Let me reword my post a bit though.

Thanks for pointing out to me that my reply came off as rude though, that was in no way my intent.
[Android] johnjjschmidt:
I didn't mean just that one. I read this whole thread and you do come off a little disrespectful. If that wasn't your intention I will believe you, however. :-)

Sent from MyGlacier.
[Android] JDV28:
Ah alright, I dont see anywhere that I have been, but i dont doubt it.

Its frustrating to have people who are really good at this, suggest ideas,

steps, etc, and not be able to do them, or want to do them. I guess my

goal wasnt clear before my last post on how I dont really need or want to

know all the specifics.
[Android] jbirdvegas:
I see what you are saying but with programming the devil is in the details. If you have specific settings you would like to change I could point in the right direction, but when you say mod/improve a general direction as to how you want to accomplish that may help.
[Android] JDV28:
Yea, thats why I moved away from Java/C++ after learning them.

I could program quite well, I just hated it lol

My first question would be, what can be done with build.prop?