yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Burillo:
Hi all!

I'm sort of new here, although i've been reading forums for quite some time now.

I have a Galaxy S (the main reason i'm here in the first place), and given i have a programming experience on different platforms i figured - what the hell. I am planning to try myself in Android apps development and possibly get down to custom ROMs and all that jive.

It is obvious where i should start with development (e.g. download SDK, read some tutorials, books etc.). As for messing with ROMs, i couldn't find an easy introduction to that. I mean, come on, everyone can root the device and install Voodoo lagfix (as i did already), but actually *creating* these ROMs is another story. If someone could possibly point me in the right direction (i just don't know where to start) it will be very appreciated.

P.S. I'm not your usual noob. I am neither afraid of command line, nor technicalities that are involved with this, and i completely understand that this will require HELL OF A LOT of reading, understanding, learning, and i completely understand that all this is way above my current knowledge, that's why i'm interested in the first place.
[Android Software/Hacking General [Developers Only]] Khalen:
I think a good start would be to search tutorials for "deodexing" as this is one of the methods to prepare a ROM. From there it should lead you deeper into the rabbits burrow.
[Android Software/Hacking General [Developers Only]] Burillo:
Thanks for the tip. Now i have questions that are probably belonging to the Chef section (started to read threads in there and realized that i should have started reading that section in the first place), but anyway.

If i compile the AOSP from source - will it work straight away on any device? Probably not, as the hardware needs drivers and stuff. So, next thing is drivers. As my device is Galaxy S, you can assume that all i ask is related to that device.

I saw that the open-source package (including the drivers) for Galaxy S has been released by Samsung. Does that mean that i can take Eclair AOSP source, copy the drivers, compile and use the result on my device? Well, probably Samsung made some modifications to the kernel, so it would be good idea to copy the kernel source too (i have never done kernel development before but i hope i have a somewhat general idea of how things work down there).

Anything else i need to be aware of?

Following the advice given earlier, i have googled for deodexing and ended up having a folder full of apk's. Does that mean that if i wish to install some Samsung stock apps (like camera) - i can take these apk's and install them as a regular app (or even include them in a resulting vanilla android ROM)?
[Epic 4G General] CJNYC:
Quick question...what is "UID 10098" and why is it keeping my phone awake? This is the first time I've seen it in Spare Parts battery history. Thanks.
[Epic 4G General] mattallica76:
Is it keeping it awake 100% of the time? Or is it lower in the list? I think it might have something to do with Google Talk.
[Epic 4G General] CJNYC:
It wasn't 100% of the time but was top of the list by a material margin.
[Epic 4G General] CJNYC:
Any ideas on this? Still having the problem.

Thanks
[Epic 4G General] mattallica76:
I believe it might be related to google talk.

Open up Talk. Hit the Menu button, hit more, then hit settings, un-check "Automatically sign in". Next, go back to the friends list in google talk, hit menu again, and hit sign out.

Reboot your phone and see if it's still there.
[Epic 4G General] churro7:
which menu are you looking at
[Epic 4G General] mattallica76:
The menu within Talk.
[Epic 4G General] CJNYC:
Thanks for the reply. That was one of the first things I did when I switched over from the EVO. Interestingly, this problem only shows up randomly. Yesterday it was a big issue and today it's not even showing up. The phone wasn't rebooted, only recharged over night. Weird.
[Droid Eris Q&A, Help & Troubleshooting] BlazinDANDAMAN:
Not sure if you guys want this here...just thought I'd post here...move if needed...

Ok, problem I've had for awhile now..

I was using Tazz 10 and Nonsensikal 7.0. They were both working perfectly then all of a sudden, I started to not receive txt messages. I can send, but not receive. So I wiped, re-flashed each ROM seperately, nothing. Wiped and nandroid to a ROM that was working, nothing.

I am now doing the Flashback 1.5 to get to Stock ROM. If still not working, gotta take to Verizon. But once it works...gonna Root again and put Tazz 12 and Nonsensikal 8.8. and see if the issue returns.

That's all, just wanted to post if any one else experiences this issue.
[Droid Eris Q&A, Help & Troubleshooting] BlazinDANDAMAN:
OK....flashed the Stock ROM...I am now recieving Txt messages...

Next...re-root and flash Nonsensikal, and see if I am still able to recieve Txts.
[Droid Eris Q&A, Help & Troubleshooting] synesthete:
After flashing a stock ROM, you should back up your APN files. One way to do this is with a free app on the market called APN backup and restore. It will back up to an XML file on your SD card. After flashing another ROM, use that app to restore the APN files.
[Droid Eris Q&A, Help & Troubleshooting] BlazinDANDAMAN:
What are the APN files for? I am stuck at boot screen since updating OTA. Haven't had a chance to root yet. So I can still do it.
[Droid Eris Q&A, Help & Troubleshooting] synesthete:
I believe they tell your phone which towers to connect to. So if you don't have the correct APN files, your phone has issues receiving messages. Some of the ROMS that are based on ROMs from other carriers may not have the right APNs.
[Droid Eris Q&A, Help & Troubleshooting] droidJW:
Shouldnt a *228, option 2, update the PRL to current for Verizon?
[Droid Eris Q&A, Help & Troubleshooting] BlazinDANDAMAN:
Well, I went through everything and now I am NOT receiving messages again. I re-rooted and flashed Tazz 12 and now not receiving Txt messages again. Damn! I have to have an unrooted phone now? This sux. I can't be with out Txt messaging.
[Droid Eris Q&A, Help & Troubleshooting] BlazinDANDAMAN:
FYI...I restored APN's and did *228
[Droid Eris Q&A, Help & Troubleshooting] Rhoman1029:
Is it with your stock txt app or did you download one? I had problems similar to yours with ChompSMS on NonSensikal. Wiped and reinstalled rom but stuck with Stock messenger and the problem never returned. If you are on stock try a different txt app. Good luck!
[Droid Eris Q&A, Help & Troubleshooting] BlazinDANDAMAN:
It was with both apps...neither were recieving. I have since restarted and it seems to be working at the moment...
[Droid Eris Q&A, Help & Troubleshooting] eriman:
Could it be that your not popular?

jk, have you turned the Wi-Fi off, cause that has seemed to work for me
[Droid Eris Q&A, Help & Troubleshooting] Rhoman1029:
I would have the problem with both apps as well but when I reinstall the rom it would work and then a little while after installing Chomp it would stop again. Finally did a reinstall and didn't install ChompSMS and everything worked and stayed working. Good Luck!
[Droid Eris Q&A, Help & Troubleshooting] es0tericcha0s:
One of my friends was having this issue too and it was due to which radio version she was using. The radio included in Tazz, KaosFroyo, and Nonsensikal were all giving her issues. She switched to xtrSense and the radio with that played nicer with her phone and all was well. Check out which version each rom runs and then you can flash the other radio over whichever rom you'd want. With that being said, I should also point out that there is a small chance, were something to go wrong with the radio flash, of damaging your phone. Now I have flashed two or three different ones, and had another friend purposely try to brick his phone by flashing radios from different phones even as well as pulling the battery while flashing a radio, and did not brick his phone. Just like rooting your phone, there's always a chance something can go wrong, but at that stage it's all about weighing the pros and cons and if you have a back up plan. Hope this helps.
[Droid Eris Q&A, Help & Troubleshooting] jmomma1203:
I'm having the same problem. I was running KaosFroyo then Nonsensikal with no issues. I switched to Tazz Froyo today and now I can't receive texts, only send them. I flashed back to Nonsensikal and it didn't remedy the problem. The radio is the same on Tazz and Kaos (didn't check Nonsensikal) so I don't think that's the issue.
[Droid Eris Q&A, Help & Troubleshooting] Delvaris:
I would like to point out that kaosfroyo doesn't include a radio it uses whatever you have
[Droid Eris Q&A, Help & Troubleshooting] jmomma1203:
Problem Solved

I found the solution here: http://xdaforums.com/showthread.php?t=770879

Hopefully it works for you as well.
[Desire Q&A, Help & Troubleshooting] slayer214:
Has anyone been able to install Busybox on the cdma desire?

I downloaded the Busybox installer from the market, but it never installs. Just reboots the phone.

Thanks.
[Desire Q&A, Help & Troubleshooting] quimpires:
Me too but gsm desire
[Desire Q&A, Help & Troubleshooting] j3sus18:
I was able to install busybox, throught i installed titanium backup.

It says, that Busybox is installed, but no icon, and i have no clue where it could be......
[Captivate Q&A, Help & Troubleshooting] MarmadukeMSB:
Not sure if there's any data one way or another yet, but I'm curious if anyone in the know has any opinions on whether or not it it's best to master clear your phone back to jf6 before moving to cognition 2.2. Does anyone think it matters? Or is it just as well to flash over whatever ROM/configuration you're currently running?
[Captivate Q&A, Help & Troubleshooting] magicdanw:
I was unable to use master clear (may have to do with running Odin in a virtual machine) so I just flashed JI6 (had been running JF7) and then did the Cognition kernel swap installation. Froyo with Cognition runs beautifully! I'll have to see how battery life is, but everything else is wonderful, and the phone runs smooth as butter (no lagfix!)
[Droid Incredible Q&A, Help & Troubleshooting] kevin217:
Hey guys, whats up.

so i have flashed just about every ROM available and i always go back to stock, for some reason i like it best, BUT i would like a overclocked / undervolted kernel to go with it and im not sure how that works.

can i flash any kernel while using the stock Verizon ROM, or is a custom ROM required?

and if i can on the stock ROM, are hydra kernels still the way to go, or is something better out that i havent seen?

thanks guys!
[Droid Incredible Q&A, Help & Troubleshooting] kungfuturkey:
You can do a custom Kernel on the stock ROM as long a you are rooted. Hydra's Kernels are good but I have had an amazing experience with KingXKlick #5 really does great battery life with overclocking.
[Droid Incredible Q&A, Help & Troubleshooting] wiobyrne:
Thanks kungfuturkey for the insight.

I'm rooted but haven't begun playing with Roms. The more I look around, the more I like what Sense has to offer me... it is one of the reasons I bought the Incredible. But, if I stick with stock... I think I want to upgrade the radio and kernel.

I noticed your recommend the KingsClick over the hydra. Have you also upgraded the radio?

Thanks.

Ian
[Droid Incredible Q&A, Help & Troubleshooting] smtom:
There are up/downsides to updating your radio, ex - worse/better reception, call quality, battery life. These vary by geography, ROM, kernel, device.

Opinions vary, and the ROM you run also makes a difference, along with the battery you use (if not stock), as well as how much/many things you synch

- take a look at the official radio thread - from there you should be able to glean what works for you.
[Droid Incredible Q&A, Help & Troubleshooting] kungfuturkey:
Yes I have upgraded the radio which is easy to do but stressful because if you do it more than once it WILL brick your phone but just do it once and your good. Hydra's kernels are good but as far as battery life goes I've had better luck with Kings #5
[Galaxy S I9000 Q&A, Help & Troubleshooting] Bellkingsway:
To give a back story on what I'm trying to accomplish, I'll explain my situation.

I work for Bell, in a retail store, the main reason I came to these forums was to find a way to re-flash phones in store to avoid having to doa what little stock we have of the phones. One of my colleagues from another location told me about the new update from Kies locking phones up at a ridiculous rate of 25%, so I'm trying to be pro-active about it.

Once I got in, I got a bit carried away with 2.2 software and what not. Now, i'm no expert, but I'm computer literate and made sense of most of the process, some extra guidance would be nice though.

Playing with the phones we have in store, I was able to flash every available software I could find on said phones, however a constant issue is found. I can not get a solid data connection. If I disable data, everything works fine, soon as I turn it back on, nothing happens.

Furthermore, I followed a thread regarding re-flashing everything back to Bell's stock settings and it didn't help me along at all.

I have done some searches, but i'm coming up dry. I know you've probably heard this hundreds of times and I'm sorry for being new to the process, some guidance towards this all would be great.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
Can you elaborate more on this?

what do you mean by unable to get a solid data connection?

what kind of data connection are you referring to?

USB cable between phone to PC?

or Wifi data

or APN (3G) data?
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
not sure where you got that number from, but it's not that accurate

the reason for the ridiculous high amount of returned phones is due the Internal SD card problem that was found.

even under normal conditions if it gets formatted a lot or used a lot it seems to die faster than its Europe counterpart.

apparently on the Canadian version of the I9000 they use a bad batch of Flash Disk for the storage memory

there is a sticky Topic Poll about it.

it is NOT the ROM flash from Kies that are killing the units, just anything software that constantly access the internal SD can produce the same effect.

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

the rest of the returns you guys at Bell are seeing are due this other problem discussed here http://xdaforums.com/showthread.php?t=775017

it can be reproduced, but you need the ideal conditions to do it.

it has to do with signal quality and tower availability
[Galaxy S I9000 Q&A, Help & Troubleshooting] Bellkingsway:
I'm referring to 3G connection. I have set up the APN, even tried different settings, all producing the same results.

In regards to your second reply, the phones I've seen at this location for DOA's have mostly because of a failure to fully turn on, the display won't show. I've experienced similar issues when a flash doesn't work properly, a re-flash fixes it. We started seeing this issue after samsung released the update. However, I'm not going to flash a customers phone to have them lose 3G connectivity, or open up other issues.

Basically, I'm looking for two things. Primarily a way to re-flash everything to work as if it were out of box, with the latest software update. Secondly, to be able to get a stable 3G connection on 2.2, everything else seems to work fine at this point.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
i'm not even going to touch the 2.2 topic as it's not even released officially.

the current stable official flash is JH2, on JH2 3G should work properly (stable), another thing you can do is to go into the service menu using the secret codes (wiki) and make sure the proper 3G bands are selected for WCDMA

1900 and 850 should both have a start next to it

next check is the *#0011* to see if the towers keeps constantly changing

that's another reason for unstable 3G if the phone keeps jumping towers every few seconds

this is also related to the 2nd link i mentioned about people getting Comatose Syndrome on the phones, which locks up the phone, and they have to reset the phone to get the phone to work again.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Bellkingsway:
I'm running JH2 currently, I ran *#2263# 850 and 1900 are available. Also, ran *#0011# both are available, ran a test on youtube it worked for 5 minutes.

Any ideas?

**Edit**

I lied, on the *#0011# it only shows 1900.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
Get something straight

the update samsung released was JH2, and it is not causing the problems you've seen.

the problems with the symptoms described are after they were flashed by the Alpha & Beta versions of Froyos 2.2, which many of them do end up losing the 850 band, the band issue can be fixed with much work.

there have been at least 4 different leaks of froyo, each one bringing its own volume of chaos and bugs, the most dangerous 2 are JPH and JPK, one loses the IMEI / ESN number ID, the other one kills the internal SD
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
Since the I9000M and I9000 are hardware based bands, you should always have the 850 and 1900 bands for 3G

Many who have tried Froyo and back had come across the problem of losing the 850 band, mainly because the Froyo leaks were intended for the Korea test team running international I9000 devices

some times just by flashing the Firmware back to stock or Froyo betas doesn't actually activates the 850 band, even though it shows as selected in the Service Menue

if you go back to the Band Selection screen of the Service Menue, you should choose bands that are knowingly not available in canada, like say band 900 for example, and then go back again to the service menu, and band selection to only choose 850

once you can confirm 850 works, then you can select 1900 as well, and now both of the bands should be active permanently until some body else screws it up again.

using *#0011# and trying to call the voice mail are the fastest way to verify for line and for 3G on 850

you can also try the app speedtest from speedtest.net

http://www.appbrain.com/app/speedtest-net-speed-test/org.zwanoo.android.speedtest
[Galaxy S I9000 Q&A, Help & Troubleshooting] Bellkingsway:
Sweet, I will try this as well.

Just a note, I have a galaxy s that is untouched, out of box and it also shows only 1900....

I'm starting to think location might be part of the issue.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
there's also this sticky

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

with additional info you can do on the phone to get 850 back
[Android Software/Hacking General [Developers Only]] cherryboy:
Hi I have a problem with my Samsung Galaxy Apollo i5801 - I followed the instructions here: ht tp://xdaforums.com/showpost.php?p=8074858&postcount=1 on how to root it, but it's now stuck at the recovery screen and when I reboot it goes straight there!! help!!!
[Android Software/Hacking General [Developers Only]] cherryboy:
Please can someone help, I have no phone :(
[Android Software/Hacking General [Developers Only]] iMand17m:
Did you tried to reflash your phone with odin ?
[Android Software/Hacking General [Developers Only]] AacidD:
press the home button
[Android Software/Hacking General [Developers Only]] grayforlife:
Froyo 2.2

Hi Im New to the site but have been flashing and hacking my droid devices for a little bit. My Q is is ther or will there be a froyo 2.2 for the zenithink epad ?

i would like to wacth netflix on it lol.

second Q does anyone have the link to flash the ZT-180 to wince ?

Thanks for the help
[Android Software/Hacking General [Developers Only]] nar3n:
try this .. youtube.com/watch?v=kml-Fzt6yUY
[G1 General] vale_arna84:
Hello, I've built an aosp froyo rom for a rooted g1. I've extracted proprietary files from a cyanogen 6 rom and build process went fine. After installing the rom either through fastboot or recovery the phone won't boot. It's stuck on g1 logo and adb does not start.

I can remove the battery and start fastboot, so I can reinstall an old rom, but I cannot access recovery.

I would like to know what kind of problem I'm facing and how to bypass it.

I'm building aosp from froyo branch as full_dream-userdebug.

Can the proprietary drivers be the problem?

I'm using G1-radio-2_22_23_02 and HardSpl.

Is there a boot log I can access to have an Idea on what's going on?

Thanks.

Valerio
[G1 General] lbcoder:
There were some kernel compatibility problems found with respect to the 0.95 series of SPLs. I suggest you upgrade to 1.33.2003. This is NOT the deathspl and you won't brick by installing it.
[G1 General] vale_arna84:
It's true. I have an HBOOT-0-95.3000. I'll upgrade to the 1.33.2003. I'm glad this is a safe upgrade. I'll give a try and let you know.

Thanks.:)
[G1 General] vale_arna84:
I've just installed spl 1.33.2003. Now I'm trying to install aosp froyo build from recovery. I receive this error:

Installing Update:

assert failed: getprop("ro.bootloader") == "1.33.2004" ||

getprop("ro.bootloader") == "1.33.0004" ||

getprop("ro.bootloader") == "0.95.3000" ||

getprop("ro.bootloader") == "0.95.0000" ||

E:Error in /sdcard/full_dream-ota-eng.valerio.zip

(Status 7)

Installation aborted.

I've also tried to install the rom using fastboot. The result is the device stuck on g1 logo as before the spl upgrade.

Any suggestion is appreciated.

Valerio
[G1 General] AndDiSa:
You should use Firerat's cutom mtd-patch and fake your SPL (in my signature you can find a link to that thread).
[G1 General] vale_arna84:
Sorry, but I can't find a precise guide on how to fake the spl following the links in your signature. Can you show me the right place?

Thanks
[G1 General] AndDiSa:
Put the following into the mtdpartmap file

mtd 90 2

spl 1.33.2005

especially the second line, then patch your recovery using Firerats recovery patcher.

(Klick on the link starting with MTD and you will be in the right thead)
[G1 General] vale_arna84:
I've followed the instruction in Fierat's thread

But nothing changed. I've done the following steps:

download FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip

create a mtdpartmap.txt with this lines:

mtd 90 2

spl 1.33.2005​

reboot into recovery

wipe cache + data

flash FR-recovery-v1.5.3-CustomMTD_S.zip

reboot to recovery

flash FR-boot-v1.5.3-CustomMTD_S.zip

reboot

flash my custom rom via recovery (fails the same way as described in a previous post) or via fastboot (device stuck on g1 logo)

Am I missing something?

Valerio
[G1 General] AndDiSa:
Did you read carefully?

You have to flash the boot-patcher after(!) you flashed the ROM, but before booting.
[G1 General] vale_arna84:
I can't flash my froyo rom from recovery neither before nor after the boot-patcher. The error is always the one posted before.

I've also tried to use fastboot instead of recovery to flash the rom, but without success.
[G1 General] AndDiSa:
Where did you put your mtdpartmap file? It must be located in the root of your sdcard.

Please read the OP in Firerat's mtd-thread carefully and follow the instructions, then there will be no problem in flashing CM6 on your phone.
[G1 General] vale_arna84:
The problem is that I'm not flashing a CM6 rom. I've just tried with CM6 and it worked.:)

My rom is a custom one built from froyo branch on aosp. Is there a way to compile the kernel telling it to accept a specific spl version?

Has anyone successfully built an aosp froyo for dream?

For the moment I'm enjoying CM6, but I need to use my own APIs, so I definitely need to flash my rom.

Maybe the best choice is to modify and compile CM6 code?
[G1 General] AndDiSa:
The boot-patcher is exactly doing that! But how big is your /system? Did you check wether 90MB will be sufficient? Probably you will need more?