yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] ro2themax:
im using a stock 2.1 rom and i do have superuser permissions installed. i also have setcpu for root users installed and "su" grants "setcpu" permission.

i also forgot to mention that i also put a "netarchy kernal" on their also which appears to me, works as it said. right now if i want to go into recovery it goes through clockwork, but i want to get amon ra's recovery on there instead.
[EVO 4G Q&A, Help & Troubleshooting] nebenezer:
hmm.. which 2.1 stock? Was it a rooted stock (with busybox and su already in there) or did you install the su app?

Although sounds like it already had busybox if setcpu is getting permission.

If you are near your computer see if you can get a # using the adb shell. I'm a little stumped here..
[EVO 4G Q&A, Help & Troubleshooting] ro2themax:
the 2.1 stock came with the "su" already. i just posted a quick update on the my previous post that i flashed a netarchy kernal on my evo also. i dont know if that helps but i just forgot to mention it...

please bare with me, im by my computer and to go into adb shell do i need to plug my evo in as charge only and open a cmd from android tools to see if i get # ???
[EVO 4G Q&A, Help & Troubleshooting] ro2themax:
i just checked and it did show a # sign...
[EVO 4G Q&A, Help & Troubleshooting] Noxious Ninja:
EDIT: N/m, missed your last post.
[EVO 4G Q&A, Help & Troubleshooting] nebenezer:
Shawnten, Sorry for hijacking your thread, I wouldn't have helped go so far off topic if your question hadn't been answered already.

-----------

Well that's a good sign (pun intended)

Maybe uninstall and reinstall your terminal emulator and reboot.

pm me if you don't get it figured out, if you want
[EVO 4G Q&A, Help & Troubleshooting] ro2themax:
thanks nebenezer....i'll keep messing with it and if i cant get it figured out ill pm you. thanks again.
[EVO 4G Q&A, Help & Troubleshooting] playya:
Simpleroot Solution

This is even easier than everything else I have seen so far, granted if you have simpleroot on your pc which is what I used 6 weeks ago, just rename the recovery file from amon to the recovery file name in the simpleroot folder (mine was ra_rec.img) and then just click on flash recovery with your phone being connected as charge only and BINGO! done in 5 seconds...

Hope it helps someone. ONly reason I did not do the terminal emulator is because the one I saw in the market said it was not for 2.2...
[EVO 4G Q&A, Help & Troubleshooting] ro2themax:
thanks, im gonna give that a try. hopefully it works out.
[Android Apps and Games] steezedout:
Nexus One, Froyo, Stock

I've been using doubletwist now for a while for a music player, however, I haven't been able to find a way for it to point to a specific folder to play. It seems that it will play any type of audio file on my SD card and it's kinda funny yet annoying to hear Let's Golf soundtracks and files playing. Anyone know how to adjust this if possible or an app that will? Same thing happened with cubed.
[Android Apps and Games] ajones7279:
Make a file called .nomedia (period included) and place it in the folders that you don't want to show up.
[Android Apps and Games] steezedout:
thanks i'll try that out and report back
[Android Apps and Games] mlbl:
Does the nomedia file work for doubletwist only or for any other player in android?
[Android Apps and Games] ajones7279:
Any player. And it works for keeping pictures from showing up in the gallery as well.
[Android Apps and Games] mlbl:
Didn't know that. Thanks for the tip!
[Android Apps and Games] gmanvbva:
Great tip. It's annoying for both pictures and audio.
[Android Apps and Games] marvin02:
There is a known bug with the .nomedia trick . If a .nomedia file is placed in a folder with existing content files in that folder will be deleted by the system the next time a media scan occurs. Try it on a test folder before you use it on a folder that has files you need (like the sound files for the GPS).
[Android Apps and Games] ajones7279:
That's weird. I've NEVER had that problem.
[Desire General] hacedms:
Hi, I've just seen that my calendar doesn't work properly, when I put it on the screen as a widget and I try to tap it to add new event nothing happens, could anybody help me how to fix it?
[Galaxy S I9000 Android Development] rocketpaul:
I've looked through the entire official froyo thread with no luck. I cannot connect to kies no matter what i do, so i would like to use odin instead. Any help?
[Galaxy S I9000 Android Development] serefo:
+1 add me to do list to I just cant connect to the kies no matter what i do...
[Galaxy S I9000 Android Development] shange:
Seems like SamFirmwares will post it tonight.

Check : http://twitter.com/SamFirmware
[Galaxy S I9000 Android Development] Richthofen:
Do not update JHC with Odin.

If you do, you will never again get straight updates from Kies..

Also current rom will not start properly if updated with Odin (unless "modified").

Working on it.
[Galaxy S I9000 Android Development] rocketpaul:
oh i see, thanks
[Galaxy S I9000 Android Development] Bandis710:
@Richthofen .. It is safe to do it with Kies ? Do you know the status of JPC ..Is it a near finished Froyo release , or also just antoher early testrelease ?
[Galaxy S I9000 Android Development] INeedYourHelp:
JHC? The froyo one is JPC.
[Galaxy S I9000 Android Development] BenF1:
Seems to me to be a more stable (however still a beta) firmware. JIT isn't enabled (when it is we'll see real speed boosts).
[Galaxy S I9000 Android Development] Richthofen:
JPC sorry ;)
[Galaxy S I9000 Android Development] iScream^:
ht*p://xdaforums.com/showpost.php?p=7914733&postcount=525

Released.
[Galaxy S I9000 Android Development] fakekullu:
It seems the samfirmware website is still not working, anybody else get this to work? :(
[Galaxy S I9000 Android Development] XlAfbk:
did anyone test flashing that with odin yet?
[Galaxy S I9000 Android Development] tameracingdriver:
Well I've just looked at and I can't see how this can work with odin... the only file in the archive is an add_jpc.tar, and then when that is opened in winrar, it contains 5 files:-

cache.rfs

factoryfs.rfs

modem.bin

param.lfs

zImage

:confused:

ETA: OK I can open the cache.rfs and factoryfs.rfs files in 7zip but still they dont contain the files needed AFAICT.
[Galaxy S I9000 Android Development] Fornowagain:
If its anything like older versions you put add_jpc.tar as the PDA file.

EDIT: Like that
[Galaxy S I9000 Android Development] vibez:
That's a pretty standard layout, all the files are just rolled into one huge tar file. Someone says flashing that tar with 512 pit worked for them

http://xdaforums.com/showpost.php?p=7915986&postcount=578
[Galaxy S I9000 Android Development] zenkinz:
don't understand? If it doesn't work, all you need is to flash back older /workable firmware.
[Galaxy S I9000 Android Development] tameracingdriver:
Thats what I am trying now, cheers.

I am always used to there being seperate files in odin.
[Galaxy S I9000 Android Development] reziel73:
i just flashed my add_jpc.tar as PDA file , without any pit , with Odin ...all is ok if someone need the rom i can post it , just tell me where and how to upload
[Galaxy S I9000 Android Development] Fornowagain:
That's good to know, although I'm going to wait for Richthofen to come back. Btw, the file is already available > http://www.multiupload.com/GEA547U9PT I have the JPD version as well from the FUD server and it's the same.
[Galaxy S I9000 Android Development] dupel:
Okay, tried to update via odin - fail. It seems that firmware flashes, but during boot cant mount DBDATA
[Galaxy S I9000 Android Development] Bobler420:
if you have a bell sgs you must change the model number from GT-I9000M to

GT-I9000
[Galaxy S I9000 Android Development] mrwookie6379:
Worked a treat for me just flashing add_jpc.tar with no pit file. Make sure to do a factory reset before hand though. :)
[Galaxy S I9000 Android Development] Richthofen:
Odin flashable I9000XXJPC rom:

I9000XXJPC_I9000OXAJPC_CODE-MODEM-CSC

Includes dbdata.rfs, so no errors will occur.

Extract .7z archive and flash as usual.

In case you have unlocked your phone or you want to use Kies in the future, I would think twice before updating...

Phone "permanent" data will be modified by I9000XXJPC rom.
[Galaxy S I9000 Android Development] DocRambone:
Can you comment more of what part will be permanent changed?
[Galaxy S I9000 Android Development] Richthofen:
The whole nv_data.bin file is rewritten.

nv_data (non volatile) is pretty much the "permanent memory" of the phone.

It contains phone production data mostly, like product code, lock information, hw revision and so on.

None of the previous roms have touched this.

Either the rom is faulty or Samsung got pissed off because unlocking.

Kies will search, allow or deny updates based on the permanent product code of the phone (GT-I9000HKAXEU) for example. I9000XXJPC firmware "destoyed" the permanent product code by changing it to GT-I9000HKxKOR, no matter what it was before.

KOR product code happens to be a "null" / test code so no updates can be found...

I would find it odd if this happened by a mistake, since it seems that the firmware also re-locks the unlocked phones, based on the comments in "Official Froyo" topic.

It was a trap, I recon.
[Galaxy S I9000 Android Development] scheichuwe:
Is it possible to backup nv_data.bin (or the complete efs folder) and restore it after flashing with ODIN?
[Galaxy S I9000 Android Development] rdy2go:
What about jp3 new revision? Does it contain the similar trap? Is it safe?
[Galaxy S I9000 Android Development] Bandis710:
Because of this permanentcode, my kies reg entry still says XEN even though i changed my productcode to xeu , to flash jm1 official ? Are you saying if i flash the new froyo release even a reg change will not let me update via kies ?
[Galaxy S I9000 Android Development] rdy2go:
And what about those who flashed jp 2 second edition?
[Galaxy S I9000 Android Development] dutchcow:
Use root explorer to make a backup of the efs folder. So in case you need it you can move those files back.
[Galaxy S I9000 Android Development] fakekullu:
This was on samfirmware's twitter page: "We don't release I9000XXJPC because flash trouble with Odin Just wait for couple more days. :)" http://twitter.com/SamFirmware

I suggest a bit of patience for guys that are looking to flash through odin.
[Galaxy S I9000 Android Development] dutchcow:
I've just flashed my phone with Odin3, after making a backup of the efs folder ofcourse.
[Galaxy S I9000 Android Development] NeoXTC:
What permanent code? Is this only for Kies? Cos I flashed JPC using Kies and then bricked my phone trying to root, so what I did was use odin to flash back to a previous firmware and flash using Kies again.

So if it's anything permanent it's seems to work as normal for me. Of course when I got the phone it's unlocked anyway.
[Galaxy S I9000 Android Development] Fornowagain:
So updating via Kies doesn't write to nv_data.bin? Mine is still on O2U product code after using Kies.
[Galaxy S I9000 Android Development] dupel:
well, considering that I just spent 3 hours trying to make Kies actually start (in the process of it I found that it left more than 2 gigs (!!) of trash on my hardrive that was not picked up by windows) and failing to do so, so I dont really want to use it in future =)
[Galaxy S I9000 Android Development] dutchcow:
I can report everything is still fine, my IMEI is the same, and so are my mac addresses. I've made a backup of the efs folder just in case. Should be fine I guess. Kies was really weird, it downloaded the firmware twice, leaving 169MB files in my temp, but the firmware updater would just disappear. Next time I won't bother with Kies anymore and use Odin3 instead.
[Galaxy S I9000 Android Development] in_nujerz:
Hey could anyone possibly post a pre rooted one I have a captivate n can't root though recovery. I understand this may belong in the captivTe forum but i if anyone has the knowledge or expertise pls post an alternatepda file or command lineprocess
[Galaxy S I9000 Android Development] kgk888:
It belongs in the captivate forum
[Galaxy S I9000 Android Development] kgk888:
What patience? It's been listed in both the major threads how to do it with odin. Theres even a link to the download.

I flashed JPC with Odin 1.3, rooted, lag fixed and have had no issues so far. Runs great but it sucks that flash comes pre-installed with the browser now. Can slow down large pages with lots of ads, not to mention we actually see them now.

Ill have to wait and see if I notice any major issues but so far everything runs fine. Haven't found any of my normal apps giving me any FCs yet.
[Galaxy S I9000 Android Development] Jeshter2000:
wich pitfile to use>?
[Galaxy S I9000 Android Development] gouroufr2000:
Is there a way to rollback to nv data without a backup ?

I've removed all files from the SDCARD to free some space... and I lost backups.
[Galaxy S I9000 Android Development] gouroufr2000:
I've found a solution to my KOR problem after a JPC firmware upgrade :

History:

I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).

Solution I found :

- Downgrade the SGS to the firmware JM6 (2.1).

- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).

- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.

- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).

- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.

- Next step : push back these 2 files in your /efs/ directory and reboot.

To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !

Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?

Hope this will help others...

:)
[Galaxy S I9000 Android Development] exadeci:
http://xdaforums.com/showthread.php?t=769400

pit 512 I used
[Galaxy S I9000 Android Development] BakaSenpai:
can you somehow explain in more detail on how to do something like this for a noob like me? thanks =)
[Galaxy S I9000 Android Development] Case_:
I don't think hacking the nv_data file by simply rewriting the product code should be considered anything even remotely close to "solution". Honestly, that seems like a pretty crazy thing to do to me. You have absolutely no idea what else is in that file and what needs to be changed for it to work properly. Why don't you just replace the file with the old one that is backed up in /efs folder? That way you at least know you have a valid file, unlike with your hack...
[Android Software/Hacking General [Developers Only]] lordvoldemort:
Hello folks,

First of all sorry for posting in wrong thread..

I was trying to flash a new rom into my htc desire.. everything went fine...

now after reboot during installation my phone has stuck on building dalvix cache screen...I waited for aurond 20 min but still gettting same thing...Plz tell me how to restore!!!

I totally scared and ****ting myself...Plz plz plz help!!!:mad::mad::mad:
[HD2 Android Q&A, Help & Troubleshooting and Genera] thenomadsoul:
Hi all,

I was wondering if there is a way to reduce screen sensitivity under android, such as it is possible to do under Windows mobile by installing proper cab files.

Indeed I have some problems while typing under android, as the screen is super sensitive and I always make mistakes. I know I should have some touchscreen problems, but it would be great to solve this problems through a SW fix, as I did under windows mobile, without sending the device to the orrible HTC assistance.
[HD2 Android Q&A, Help & Troubleshooting and Genera] thenomadsoul:
anyone knows how to reduce screen sensitivity?
[HD2 Android Q&A, Help & Troubleshooting and Genera] somerandomname:
im wondering the same thing since i got this cheap charger which makes the sensitiving horrible, but back to normal when i unplug it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] fruchtfliege:
android made my faulty touchscreen much more usable than stock winmo. but you are right: typing with standard keyboard is also nearly impossible for me! that's why i use swype. my touch is jittering around every few minutes. at this moments it's better for me to wait until it's over...

at least: +1 for a lower touchscreen sensitivity under android!
[HD2 Android Q&A, Help & Troubleshooting and Genera] squish099:
I don't think I would use that charger it providing the wrong volts or amps (sorry don't remember which) but it will cook the digitizer, happened to my g1 using an old motorola charger for a couple days while camping

Sent from my HTC HD2 Android
[HD2 Android Q&A, Help & Troubleshooting and Genera] Simonnn:
I know exactly what you're talking about, as I suffer from it as well. HTC did release the patch for winmo which fixed the problem completely.. hope someone finds a fix soon, I have not been able to find one! :(
[HD2 Android Q&A, Help & Troubleshooting and Genera] hoss_n2:
the screen problems i faced disappeared with android , i think your devices have hardware faults
[HD2 Android Q&A, Help & Troubleshooting and Genera] thenomadsoul:
bump on this! :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Archer:
rofl :p
[HD2 Android Q&A, Help & Troubleshooting and Genera] fruchtfliege:
yeah, i know that my touchscreen is a bit faulty. at cold weather (like now) and cold hands, it is nearly unusable for writing :( but under winmo the jitterbug wasn't that annoying after sensitivity reduction! that's why we are looking for it on android.

what kind of patch is it? does it fix somehow the jitterbug of faulty screens, or just reduces the sensitivity like several mods on winmo does?
[HD2 Android Q&A, Help & Troubleshooting and Genera] AngelDeath:
Anyone tried changing the sensitivity setting on the HD2?

Go to All apps/Settings/Language & Keyboard/Touch Input/Text Input/ then scroll to the bottom for Calibration Tool. There you can change the touch sensitivity.
[HD2 Android Q&A, Help & Troubleshooting and Genera] white-energy:
My touchscreen is faulty too.. i hope Hastarin will make for us a special Kernel to fix this issue.. i just have to wait till that jitterbug ends, then i could type... :(

same in-games..
[HD2 Android Q&A, Help & Troubleshooting and Genera] thenomadsoul:
I can only make calibration, I can't see a way to directly reduce screen sensitivity

+1 on asking astaring for a kernel with reduced sensitivity :)

The probem is that if we send the telephone to HTC they will simply upgrade the ROM to the 3.14, as in the new official ROM the sensitivity has been drastically reduced and the problem doesn't appear anymore...

but under android it is still present (and the touch screen remains faulty)!!
[HD2 Android Q&A, Help & Troubleshooting and Genera] AngelDeath:
thenomadsoul = I can only make calibration, I can't see a way to directly reduce screen sensitivity

If memory serves me right, a keyboard with words for you to type appear, from what I know cause I have done this, the harder to press the less sensitive the screen is to touch, the lighter you press the more sensitive it is to touch.

If im completely off base, then take me out to the pasture and shoot me :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] thenomadsoul:
Thanks mate, I will try this and let you know ;)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Bisis:
Keep this thread alive!!

Any update about what already discussed?
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Same. Any update?
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Tried Magldr 1.13 and Clockwork 1.3 updates.

Used HyperDroid and ghost touching was just as bad, though it took a while.

Tried Typhoon mod and it had same issues.

Using Stock Gingerbread and it's still giving some indications but not so bad.

It seems like the screen is just way too sensative. I'm out in the wind and the screen somehow picks up the wind hitting the screen as me touching it?
[HD2 Android Q&A, Help & Troubleshooting and Genera] rodpelosini:
Is this a Hardware Problem?

I´m using Android in my Hd2 too, version gingerbread from nexus one by tytung...

I had problems with screen sensitivity in WinMo, and for now in Android os...

So, maybe this problem is a hardware issue? If try replace screen, this problem persists?

In HD2 plus Android, this device is great... except screen sensitivy.

Sorry about my poor english.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Bisis:
I'm not sure it's a sensitivity problem.

Rather I think that to use screen we have to press keys on the touch with almost strong strength.

What I think is that sometimes it seems HD2's touch doesn't clear the buffer of pressed coordinate... and it starts to press here and there randomly.

Or it seems there is some strange signal which causes this.

I think lowering touch screen sensitivity won't solve our problems.
[HD2 Android Q&A, Help & Troubleshooting and Genera] white-energy:
it will.. on winmo, the latest update fixed the sensivity problem.. and the screen stopped jumping arround
[HD2 Android Q&A, Help & Troubleshooting and Genera] ftd01:
Is there any solution on Android?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Bisis:
I'm waiting too..

I hope the problem has not been forgotten
[HD2 Android Q&A, Help & Troubleshooting and Genera] Major_Sarcasm:
See here. It can't be completely fixed with software, your hardware is faulty. I had exactly the same problems. New screen, completely fixed, done under warranty. It felt like a completely different phone, seriously it was brilliant (and still is).
[HD2 Android Q&A, Help & Troubleshooting and Genera] white-energy:
Can any developer take a look at this..

Seems like the sensivity of the Gsensor is high.. is the touchscreen relied to the gsensor?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Bedwej:
Bump, definitely want this sorted out, my phone is practically unusable, the screen is so sensitive. It gets worse in winter when it's colder.
[HD2 Android Q&A, Help & Troubleshooting and Genera] white-energy:
You will have to live with it.. there's nothing we can do =/
[HD2 Android Q&A, Help & Troubleshooting and Genera] :
Maybe we can modify surfaceflinger.so and surfaceflinger_client.so, I also noticed, like some people, there are different sensitivities when I switch to builds from different devices..
[XPERIA X10 General] mezo9090:
well done.. at last .. no more spam in topics
[XPERIA X10 General] im_iceman:
Thank-you PiLoT... all three of those were driving me nuts! People seem to think that this is an unmoderated site and they can do and say what they want.. so i'm pleased to see some decisive action!
[XPERIA X10 General] damirbusic:
Thank you, finally !

2.1 upgrade topics could also be filtered.

http://xdaforums.com/showthread.php?t=769198
[XPERIA X10 General] iead1:
What if I wanted to make a thread talking about how the lack of multitouch caused the low in-call volume to drain the battery while *****ing about how the lack of Android 4.3 on the device created these problems?
[XPERIA X10 General] -PiLoT-:
Then I delete it and warn you
[XPERIA X10 General] roaringhere:
Very good... Those are annoying post...
[XPERIA X10 General] -PiLoT-:
updated to include stuff about 2.1