yashsingh1/xdaforums huggingface dataset:
[Gen8 Android Development] chrulri:
Hey dogmaphobia

Next firmware has been release, so here is the updated version:

avos_2.1.02_temproot.zip

Have fun :cool:
[Gen8 Android Development] computerfreek:
Thanks for the update chulri ! Love having root on my archos 32 even if it is temp root . Great work thank you .

Maybe you can post this update with the new firmware link . Alone in it's own post so others can find it easy.

Thanks
[Gen8 Android Development] chrulri:
@computerfreek

here you go: [HOWTO] Root easily your Gen8 device (fw 2.1.02) (including mirror links)
[Gen8 Android Development] spino1970:
Any news about modded kernel for overclocking on 2.3.26 FW?;)
[EVO 4G Q&A, Help & Troubleshooting] samrozzi:
im looking for a way to tether my phone either wifi (preferable) or usb to my laptop but he difference is, I want it to do 4g. I dont think th wifi tether app doesnt do 4g. And I know some roms have sprints hotspot app but I dont want to pay and use that. Is it possible to crack the official sprint app to be free? or something similar?
[EVO 4G Q&A, Help & Troubleshooting] IcerJo:
Are you rooted? If so then you can use the Wireless Tether app it does allow you tether usin 4g as a internet source. Just make sure that you turn 4g on and let it connect before you start the wifi tether. their might be a few others but this one has yet to fail me. also I believe that sprints/htc's wireless hot spot and the usb tether are 3g only (least if your running custom roms).
[EVO 4G Q&A, Help & Troubleshooting] scottspa74:
Yeah, on the roms with wifi hotspot enabled you don't have to pay, the code is broke. Not sure about 4g though, haven't tried. As other poster said, wireless tether on market is solid.
[EVO 4G Q&A, Help & Troubleshooting] nintennuendo:
On wireless tether i had an issue with cutoffs and disconnects. I fixed it by changing settings to channel 1. Not my tip, im just sharing it
[EVO 4G Q&A, Help & Troubleshooting] IcerJo:
I could never get the broken/fixed sprint hotspot to broadcast 4g, I'd start 4g before starting it and it kicks me out of 4g even when I try to restart it it wouldnt let me use 4g at all. But as soon as I turned off the sprint hotspot my 4g connects.
[EVO 4G Q&A, Help & Troubleshooting] JTNiggle:
The verification for 4g hotspot is different and hasn't been cracked yet. So, the built in hotspot will NOT allow 4g tethering. It will go into a scan/connected/scan loop as long as the hotspot is active.

Wireless Tether and Easy Tether are both in the market and will allow 4g tethering without issues. I have both installed and use them most every day to tether 4g, works great.

Hey... I think this thing makes phone calls too!
[EVO 4G Q&A, Help & Troubleshooting] playya:
pdanet it works great and supposedly fastest 4g connection from USB out there
[Galaxy S I9000 Android Development] ykkfive:
hi all,

i found that with jpx there r some bugs, and the files are easily corrupted. and i have found a lot of errors in the log even with reflasing it again and again

- 12-20 15:10:19.017: ERROR/SQLiteOpenHelper(2854): Couldn't open external-81b6140f.db for writing (will try read-only)

this file gets corrupted every 2 or 3 boots

- browser has max 4 tabs? (this is not a bug)

- symlinks will be damaged

- dalvik cache are vulnerable

- db-journal under dbdata is a mess

anyone have these kind of problems?

and one more error found:

12-20 15:15:00.017: DEBUG/skia(3181): ------- write threw an exception

12-20 15:15:00.021: WARN/System.err(3181): java.io.IOException: file is too big.

12-20 15:15:00.021: WARN/System.err(3181): at android.webkit.WebView$CountingOutputStream.write(WebView.java:9241)

12-20 15:15:00.021: WARN/System.err(3181): at android.graphics.Picture.nativeWriteToStream(Native Method)

12-20 15:15:00.021: WARN/System.err(3181): at android.graphics.Picture.writeToStream(Picture.java:119)

12-20 15:15:00.021: WARN/System.err(3181): at android.webkit.WebView$7.run(WebView.java:1705)

12-20 15:15:00.021: WARN/System.err(3181): at java.lang.Thread.run(Thread.java:1096)

EDIT:

one of the problem areas http://xdaforums.com/showpost.php?p=9959176&postcount=47
[Galaxy S I9000 Android Development] ragin:
What does this mean for those of us using JPX?
[Galaxy S I9000 Android Development] ykkfive:
if they r bugs, your data/files are fragile. and in turns not usable
[Galaxy S I9000 Android Development] cHarOn99:
@ykk_five are you using ext4?! i had that issues also but not with jpx, also corrupted files on external sd card and so on, i am now back again at RFS since JPU and have not such issues anymore
[Galaxy S I9000 Android Development] ykkfive:
i;m using ext2 (i didnt use rfs actually), but i didnt have these kind of problems in any other rom b4

also my ext sd has no problem, only data and dbdata are affected
[Galaxy S I9000 Android Development] s88:
I am using DOC v5.1 JPX

RFS on Voodoo 5.03

Verified Internet Browser max is 4tabs only.
[Galaxy S I9000 Android Development] ykkfive:
actually some problems are not visible to users, but if u open ddms/logcat to read the log, u can find a lot of db problems
[Galaxy S I9000 Android Development] cHarOn99:
ext2 can easy corrupt data, i had also long time no issues with ext4 anyway it started to give me issues, because since JPU RFS is fast enough and smooth i see no reason to use any of the "lagfixes" anymore.
[Galaxy S I9000 Android Development] ykkfive:
yeah i know ext2 is fragile, but those problems occur while the phone is on and running
[Galaxy S I9000 Android Development] cHarOn99:
checked with logcat and can't find any db issues on my side
[Galaxy S I9000 Android Development] .Slane.:
As XXJPX doesn't use ext2 out-of-the-box, blaming this ROM is nearly irrevelant.
[Galaxy S I9000 Android Development] Auzy:
Exactly Slane. It's like saying your pen is of poor quality, after using it as a crowbar to pry something open. Or saying OSX broke your hardware after using your Macbook air as a hammer.
[Galaxy S I9000 Android Development] g00ndu:
Noobs... Sighz.......
[Galaxy S I9000 Android Development] .Slane.:
Yeah nearly 1000 posts here and unable to post something with some interest ? Ext2 especialy with loop have problems and it was before XXJPX and Samsung have "tricked" lag using internal NAND for faster response time.
[Galaxy S I9000 Android Development] spandsbab:
This dude has a point actually...

This one did not really seem to help...
[Galaxy S I9000 Android Development] alain57:
you know that ext2 has no journaling ...

if the phone turn out, without the filesystem beeing umount then IT IS NORMAL that you have these bugs ....

it may be possible that samsung did not umount the filesystem on shutdown
[Galaxy S I9000 Android Development] danzgrace:
hardcore's ext4 default settings will hopefully solved this issues.
[Galaxy S I9000 Android Development] ykkfive:
yes, no umount will be done on every reboot/shutdown

and as i said these problem occurred when the phone was running also
[Galaxy S I9000 Android Development] sunwee:
sigh...noobs. do you even know who the TS is? ykk_five is one of the more knowleagable persons around here, even if he doesnt post a lot.

he was one of the first to present the loop lagfixes, and later contributed to the ext2/4 lagfixes and also was instrumental with the finding which led to more usable ram for froyo (which found it's way into ULK, voodoo and other kernel tweaks).

although so far i havent face any problems with JPX like those he mentioned, i wouldnt dismiss his comments just like that. maybe he was a bit quick to announce but that doesnt mean you guys can slag him like that.

let's just let the investigations go on for a while.
[Galaxy S I9000 Android Development] ykkfive:
thanks sunwee, i'm really appreicated that someone remember me for those tiny findings

anyway, i wanted to let ppl know jpx may contain some bugs, which wont happen on other roms
[Galaxy S I9000 Android Development] Bynar010:
Sorry but if you are using ext2 you are running these risks. Pointing fingers at the rom is bordering on scaremongering all those who have moved to jpx.

For the record I'm on voodoo ext4 with no issues at all on jpx.
[Galaxy S I9000 Android Development] .Slane.:
Ok, I've purged log file, made 10 reboot (wait time between each reboot in script is 120 seconds), no db error reported so far. I've flash my JPX with a repartition before, ykk_five have you do this with your reflash ?
[Galaxy S I9000 Android Development] ykkfive:
no i didnt repartition it when flash, i'm now writing zeros to the disks to see if there r any bad blocks

anyway, thx for the test result
[Galaxy S I9000 Android Development] cHarOn99:
i currently can't see a fault or issue on the rom, i think one source is not enough to come to that conclusion, also the result is with ext2 which can cause also unexpected issues, next point is, maybe there is also a custom kernel used which again could cause issues, many things makes the Statement not very usefull.

I also think that ykk_five is experienced, but anyway that doesn't help in that case :)

So in my eyes you can only come to such statement if you test with stock JPX, RFS, no tweaks, .........
[Galaxy S I9000 Android Development] .Slane.:
I'm NOT sure that 10 reboot is enough, if another problem arise like the /system corruption with some mount options, we'll face it perhaps in some days. But for my curiosity, why using a lagfix especialy ext2 with newer ROM like JPU and JPX ? I didn't face any application which need it, perhaps only to check consistency of filesystem ? There's numerous people who apply lagfix even with JPU because older ROM need it.
[Galaxy S I9000 Android Development] ykkfive:
yes, i'll try to see if these problem exist in some other combinations, and since i'm using my own modded kernel, so i'm sure that with the same configurations and tweaks it was working fine b4 jpx
[Galaxy S I9000 Android Development] ykkfive:
i chose ext2 coz rfs is very slow, in my opinion, even in 2.2.1

and in quadrant, jpx only score 1.xk in IO but i'm having 7k+ without OC
[Galaxy S I9000 Android Development] cHarOn99:
i really would suggest to make tests with default JPX, also as .Slane. said, flash the stock JPX firmware with pit 512 and repartition checked, oh forget about it you first need to flash JPU with repartition checked, after that flash JPX without repartition.

If you still see the same issues then there could be also an hardware issue with your SGS, but first it will for sure make the result easier to coem to an conclusion.

I will also check logcat frequently today.
[Galaxy S I9000 Android Development] ykkfive:
yeah, perhaps i'll try rfs on jpx again
[Galaxy S I9000 Android Development] KMino:
Maybe,

Haven't had JPX on it for long, installed it today.

That said, I use Doc's ROM. I was on JP8 with ex4, I rolled over to JPX with ex4 in place with a no-wipe install :D Also installed Speedmod K11B, etc at the same time.

I've updated a few apps, copied over a lot to the sdcard, rebooted a few times, played around with /system files and rebooted a few times.

All is good, no errors in the logcat so far.. Anything happens I'll post here :rolleyes:

My guess, NJ FSystems might have been compromised by the speed up for RTF??
[Galaxy S I9000 Android Development] psynapse:
Think slane nailed it:cool:
[Galaxy S I9000 Android Development] spandsbab:
Well I think he did have a point and now he is trying to help ykk_five sort out the problem and yeah both of our posts are quite useless:D
[Galaxy S I9000 Android Development] g00ndu:
Hi, I agree. he has a point. Since when did he blame the rom? He highlighted the issues and just asking if anybody is experiencing those issues as well.

But he had jumped the gun saying that ykk_five had blamed the rom.

Edit: As the thread progresses, I can see that he has tried to help and simulate some studies, which to me is helping him. This, I respect him for that.
[Galaxy S I9000 Android Development] .Slane.:
Sorry if I was a little "hard", but I found the first post not really rigorous. ykk_five pointed that he had re-flash several times the XXJPX and seems ti always have these errors. I've quickly tested some reboot in stock XXJPX file-system (all RFS) and didn't see this kind of corruption. I had numerous problem in ext2 some years ago on computer and many was related with the lack of journal mode, so I really no more trust this file-system (and prefer FreeBSD with UFS+FU, but not really SGS related).

It can be very interesting if ykk_five can find how have this problem in JPU, because it's the first 2.2.1 ROM we have and have the change for data application. Perhaps JPX have really a problem but we must be very careful how ti detect it to prove that the "stock ROM" have file-system problem. However, his findings can perhaps keep away people from ext2 in conjunction of JPX, preventing data loss.
[Galaxy S I9000 Android Development] s88:
7k??? :D:D:D

please share the method
[Galaxy S I9000 Android Development] ykkfive:
actually i prepared to share it, but due to the release of 2.2.1, i had to make changes accordingly.

maybe it's lucky that 2.2.1 just came out on time, otherwise if it's not working with 2.2.1 then i'll be in trouble
[Galaxy S I9000 Android Development] cocchiararo:
ïs it some "cheat", or does it really ups real world performance ? :P
[Galaxy S I9000 Android Development] hardcore:
The FSR & RFS drivers in XXJPU & XXJPX have been updated - that's why RFS is faster on these roms vs older ROMs (although still not as fast as ext?).

Another thing that I noticed is changed, is that the FSR now supports write barriers on stl* partitions. Previous versions did not. U can see this if u use ext4 with barrier=1. In previous kernels, in dmesg, ext4 will report that write barriers are not supported for stl* partitions (dbdata, cache). But using the XXJPX drivers, it doesn't show this warning anymore.

My point is, if write barriers could change, other things could change as well.

Anyway, I think although ext2 is going to be lighter than ext4, the current settings I'm using for ext4 is light, fast, good on battery and still safe.

The settings are: ext4 data=ordered, no delayed allocation, barrier=1, commit=20s.

data=ordered + no delayed allocation + barrier=1 => safe

commit=20s => less battery usage
[Galaxy S I9000 Android Development] ykkfive:
yeah i remember some options were ignored b4

but when i listened to mp3 and surfed the internet with ext4, it was so lagged so i gave up ext4
[Galaxy S I9000 Android Development] ykkfive:
some simple tests results (/system is using rfs):

1M file write 100 times

bash-4.1# time for i in `seq 1 100`; do dd if=/dev/zero of=/system/test count=2000 &> /dev/null ; done

real 0m8.344s

user 0m0.242s

sys 0m8.031s

bash-4.1# time for i in `seq 1 100`; do dd if=/dev/zero of=/dbdata/test count=2000 &> /dev/null ; done

real 0m1.787s

user 0m0.133s

sys 0m1.652s

write 100 10k files

bash-4.1# time for i in `seq 1 100`; do dd if=/dev/zero of=/system/test$i count=20 &> /dev/null ; done

real 0m0.346s

user 0m0.051s

sys 0m0.297s

bash-4.1# time for i in `seq 1 100`; do dd if=/dev/zero of=/dbdata/test$i count=20 &> /dev/null ; done

real 0m0.251s

user 0m0.039s

sys 0m0.207s
[Galaxy S I9000 Android Development] cocchiararo:
i guess the ones with better results are "yours" ?

just want to clarify something tho... i NEVER wanted to call you a cheater or anything, and i still haven't received my i9000

I just asked about "cheating" cause a couple weeks ago i tried a "data2ext" trick on my nexus one, that performed like... bad :P (tons of lag all the time), but had a cheat for quadrant, that made it look really good.
[Galaxy S I9000 Android Development] ragin:
I am sad it got moved to Q&A. It won't be noticed much here. It actually belongs to DEV. BTW, Are all lagfixes with ext2 affected by this?
[Galaxy S I9000 Android Development] ragin:
If only ykk_five had put a [REF] tag on the title. This is a reference material to the developres.
[Galaxy S I9000 Android Development] sirphunkee:
I think this is directly useful for enough dev's that I'll go ahead and put it back into the dev section as a reference.

Thanks to everyone involved in digging and working through this in an effort to get some useful data out of it.
[Galaxy S I9000 Android Development] ragin:
WOW & WOW, Thank god this came back to DEV.
[Galaxy S I9000 Android Development] ragin:
Are all lagfixes with ext2 affected by this?
[Galaxy S I9000 Android Development] ykkfive:
i think i've found something about the problem (partly i think). it was the mediascanner, and perhaps more services, which tried to convert and upgrade the db but caused an infinite loop if the conversion was failed or the db was not readable

so if i'm correct, all fs will be affected
[Galaxy S I9000 Android Development] ykkfive:
yeah i know what u mean. i didnt "intentionally" do something for getting higher quandrant marks, but i think the changes i've made to the system will affect the result (of coz).

for the lag things, i can say no lags, with less than 20 apps installed, but the only exception is when i'm typing with the keyboard in the browser, it is so lag and still not fixed yet
[Galaxy S I9000 Android Development] DamianGto:
Well i did try to find any errors with logcat, but i dont.

So to blame jpx and ext2 is not right.

I guess this is a different fault you got on your phone.

So lets focus on whats happens and stop blaming jpx or ext2.
[Galaxy S I9000 Android Development] ragin:
How serious is this?
[Galaxy S I9000 Android Development] dk206:
you shouldn't even be on JPX it was just a beta, JPY is official. And its fixed a number of bugs written on here.
[Galaxy S I9000 Android Development] ragin:
If Samsung fixed it, verify and say so on the Title
[Galaxy S I9000 Android Development] Auzy:
Source? I didn't think either had even begun rollout honestly. I also recall people saying "JPC is final" in the past too.. So please verify this claim..

Also, last I checked, I don't believe we had a changelog either. So, please also verify the claim that "a number of bugs written here" is fixed.
[Galaxy S I9000 Android Development] phalanger:
Actually JPX is isnt a beta. JPU was a leaked 'beta', JPX was officially released and source was released also (no source for JPY so far, but it is assumed to not differ much)
[Galaxy S I9000 Android Development] Rawat:
What does browser having 4 tabs max have to do with IO/db problems/bugs?
[Galaxy S I9000 Android Development] ykkfive:
my fault, 4 tabs is not a bug

and for the 'IO/db problems/bugs', i think it's not for jpx only. and as i said, i cannot solve the problem but only to prevent it from happening. may be that's why some new modded roms prefer to wipe the /dbdata
[Galaxy S I9000 Android Development] karl999999:
please give more exact info

i still dont understand, after reading all the posts in this thread.

is there a confirmed problem that everybody has?
[Galaxy S I9000 Android Development] DamianGto:
No

**Using my own JPX kernel, z4mod, 345MB Ram and ext2 filesystem**
[Galaxy S I9000 Themes and Apps] keno_ro:
I would like to have the .apk for the Voice search program with the training option.

I'm not a native english speaker so my english is not Cambrige like.

As far as the article states its available only to US.

http://www.mobilecrunch.com/2010/12...for-android-can-now-be-trained-to-your-voice/

Thank you!
[Galaxy S I9000 Themes and Apps] emreeris:
Hi Guys, While trying to start the Market app for the past few days, I get the following error message:

Sorry!

The application Market (process com.android.vending) has stopped unexpectedly. Please try again.

This started after I upgarded to Froyo 2.2.

Is there any known issue about this problem?

Thx
[Galaxy S I9000 Themes and Apps] dreamhole:
i have same problem :(
[Galaxy S I9000 Themes and Apps] photoman1966:
after upgrade you need to do the factory reset, it will fix all of your problems with the market gps and other applications, let us know how it goes. good luck
[Galaxy S I9000 Themes and Apps] lgkahn:
i had that problem on jp2 2.2 havent had it on jpy 2.2.1

in manage apps/clear cache didnt' work.. try that first.. if it doesnt work

(this is for market_ try uninstall updates..

it usually happens if there is a hung update killing the queue.. . for some reason it then works after you uninstall updates. and then the updates reinstall anyway.
[Galaxy S I9000 Themes and Apps] nalinbhatt:
Had the same problem with stock internet browser after updating to froyo (JK4, Bell canada). I did factory reset then eveything is fine now. Hope it does not FC itself again.
[Galaxy S I9000 Themes and Apps] ickyboo:
Got the problem too. Tried downgrading 5 versions,cleaning cache then manually deleting setting, changed kernels. No good. I give up. Market can kiss my ass
[Galaxy S I9000 Q&A, Help & Troubleshooting] gabloammar:
Hey guys.. Ummm.. I had a completely, perfectly, fine rooted Galaxy S. [I don't know if it's still rooted or not]

I'd installed Darky's ROM [5.6], and was gonna put in 6.0.

I decided to do a completely clean install for some reason [I don't know, I'm stupid.] and there's where I made the mistake. The phone got flashed n all through Odin, but now my 3 button combo doesn't work.

I searched for a fix, and it requires adb if I'm not wrong. Problem is, adb itself requires busybox and superuser. I don't have superuser in the phone [I suppose I can find it in the market, haven't checked.] but I was installing busybox, and it said that my phone's rooted but something's wrong [something about a nand or something] and that busybox can't be installed.

I want that ROM and I want my 3 button combo working again :(

Can someone please help? :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] ragin:
Which ROM do you have now? If its Darkyy's, its pre-rooted, & has busybox.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gabloammar:
Umm.. I don't think I know. :(

I just flashed the thing with this.. 'h t t p : // w w w. multiupload . com / XWDSKCPGTD' and the JM1 CSC file.. :(

But it's certainly not Darky's..

Though I DID put in the 6.0 .zip file in the internal memory. Haven't installed it though [more like CAN'T install it :(..]
[Galaxy S I9000 Q&A, Help & Troubleshooting] ragin:
Download Tuxility from the market. It has a Thread here in Dev too. You get options of normal shut down, reboot into recovery & into download.

Hope this helps.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gabloammar:
I tried that :(

It doesn't start :( Force closes :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] ragin:
Have you tried Quick Boot from the market?
[Galaxy S I9000 Q&A, Help & Troubleshooting] gabloammar:
Yep. I installed it, opened it, pressed Recovery.

Nothing happened :(

[in the description of the app, it said that root access is needed for it to work, and since the buttons weren't working, I think the phone's not rooted anymore]

I even pressed Download. Nothing happened there either :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] ragin:
2.1 ROMs have a different way of entering into recovery & download. You press Vol up + menu + Pwr keys, & you get the splash screen, release the Pwr button for half a second & again keep it pressed till you go into recovery.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ragin:
Otherwise, there is manual way of installing the superuser & busybox, you need to search the forum.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gabloammar:
Umm.. It says it's 2.2 :(

Still think I should try what you said?
[Galaxy S I9000 Q&A, Help & Troubleshooting] gabloammar:
I'll try that too :( thanks like THIIISSS much for helpin! ><
[Galaxy S I9000 Q&A, Help & Troubleshooting] gabloammar:
The splash thingy didn't work :( I'll look for the superuser and busybox threads.. Bet I won't be able to fix this :(

Thanks again :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] ragin:
For 2.2 you keep holding all the three buttons till the flash screen blanks & comes on, on the second blank screen, release the pwr button. If that doesn't work, try to do it at the third blank.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gabloammar:
I pressed the menu and volume button simultaneously while the animation was going on, and I got this screen saying 'FORCED UPLOAD by KEY PRESSING' and a bunch of values on top [in red].

Apart from that, nothing :(