yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] [] AL []:
In China: yes I am indeed.

Interesting point and reading...although I used the GPS and LocusFree before with good accuracy.

BUT, I redid my math, re-checked and compared with previous tracks recorded on Froyo and I was wrong: the offset is about just 50 meters like previously reported by somebody else. So SORRY ABOUT THAT ONE. Me bad!

But the fact remains that while recording, the location was way off like nothing I've seen before [not very usefull for orientation]. Once I stopped recording and checked the track record it was decently displayed... So the next time I'm lost, I might just have to record the track for a while, save it, close and restart Locus to find out where I am... :p Anyway, I will test more and read that article with more attention.

Sorry again for the erroneous numbers I posted on previous post. :o
[Defy Android Development] xanadu:
Same here +Picme: FC
[Defy Android Development] ccav2000:
@[] AL []:

Oh, you are really on China?! I apologize to the previous poster that said so then.

The 50m error was first reported by myself, the last test I did only 30mins ago, showed me 100m away! The reported accuracy was 10m, obviously completely false.
[Defy Android Development] [] AL []:
Hehe, yes in the land of absolute no skill car drivers.

Well, like I said, I will experiment a bit more on this because altough I was always dead on for my location at home on Froyo, the accuracy of actual bike ride tracks was always a bit off pre-CM7. And that, I don't think is due to the fact that locations are mucked in China like mentioned on the link given by bobo9900. Which BTW doesn't seem to be very trushtworthy [the discussion thread, not bobo].

Also, always keep in mind that GPS accuracy is always influenced by the quality of the received signal [and the hardware] and that anything can affect it: trees, clouds and (like it is almost the case here in town) high-rise buildings. I suspect that in the end, the Defy's GPS hardware is just not that great and that CM7 is really not responsible for much of our problems here...

But again, I will run more tests and and even go back to Froyo if needed: I need as trusty of a GPS that I can...
[Defy Android Development] bobo9900:
Its okay. I myself had not flash this ROM yet, so I can't say much.

But regarding China map offset, it had been long known issue. Best way to know if it really exist is to flash stock ROM and compare with CM7.

While I google, I found other reference.

http://home.wangjianshuo.com/archives/20081109_all_maps_in_china_are_transformed.htm

Don't know if its true or not.

And if countries other than China have offset problem, then maybe CM7 GPS needs fix.
[Defy Android Development] ofmb:
i think the read_ahead trick is great only on boot time when there's a heavy multiple reading of varios files.

in real system use its bad as most apps read eventually the whole file and even 128kb read_ahead minimizes the disk_access by hundreds

maybe its possible to change the read_ahead value just before UI & apps start to run -

when the phone vibrates might be a good time..
[Defy Android Development] [] AL []:
bobo9900: I've read what you refered too and I don't believe much of it...all conspiracy theories without real solid info to back it up. Maps are relatively precise and I don't beleive that there is a intentionally induced map offset in China.

I just went in my map application and tried about 12 different map styles/providers and the only one that I saw major problems with was Google Classic (hence the 300-400 meter offset I originally posted). All the others, including Google hybrid/satellite, are dead-ON within the Defy's given accuracy.

So I would definately want to remove my alarmist GPS innacuracy post: the problem is Google Classic map only.

So bobo9900: stop searching internet for false info :p and go make a nand backup of your current build and give CM7 a try :D. You will not regret it. thanks for trying to bring some light on the map subject though.
[Defy Android Development] ccav2000:
I still think that the GPS can do better than this. People report that it works better with the official Froyo, and one user report better accuracy with the latest MiUi ROM.

I tried setting Google Maps to Sattelite, was showing my possition in the middle of the street. Only problem, the next street from the one I was actually on!
[Defy Android Development] bobo9900:
Currently I need a stable ROM. I'll switch to CM7 as soon as it is RC or stable.

I'm interested in GPS too, so I wanna make sure everything is okay.

Last link I gave is not all about conspiracy theory ;) but rather maybe different maps vendor uses different map projection, thus different offset.

It's good to know that GPS is okay.. eagerly waiting for a stable CM7 :D
[Defy Android Development] ccav2000:
Different MAP projection? No my friend, same Google Maps version running on my old LG GT540 has much better accuracy that the Defy running CM7. It is not the application's fault.
[Defy Android Development] hailmary:
camera zoom

im on 110530-0009.vid rec wide dont show black screens & photo shows all zooms no more chopped on 4x+...now is better quality.
[Defy Android Development] ofmb:
would you post the two gps.conf files from the lg and moto?

i'd like to compare them.

i use

ACCURACY_THRES=5000

which works great for me.

maybe you should have something like

ACCURACY_THRES=2500

and another thing - just confirm that the two lon/lat are really different.

just post the difference between them if you dont want to reveal your location.
[Defy Android Development] ccav2000:
I'll try, probably later today or tomorrow, I don't carry the LG with me, it stays at home.

Tried ACCURACY_THRES=5000 to the gps.conf, no effect.
[Defy Android Development] Epsylon3:
for the read_ahead_kb buffer : can be tuned in :

/sys/devices/virtual/bdi/

for each block device, separatly

devices 1:x are ram0 to ram15

devices 179:0 is SDCard, and 179:32 is internal flash

its set to 0 to sdcard, 128 to internal flash (and default)
[Defy Android Development] ofmb:
yes - in the last two days i'm checking 179:0 - read_ahead_kb=2560

since changing it no problems in sd_card (16gb) like few of us had.

which devices participate in boot process?

you think it's possible to change values after boot is done in one of the boot scripts?

that way we'll have fast boot + responsive OS.

right now i'm using setVsel speedfix as a workaround for echoing the value to 179:0
[Defy Android Development] ofmb:
have you tried this?

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

and change ACCURACY_THRES=2500 so you won't have inaccurate fixes.

then try with lower values - which will probably increase fixation time.

btw - how long it takes till you have a fix?

and another very important thing - find a good ntp server!

i used "SNTP Client" from market to benchmark ntp servers i found in google.

use "argentina ntp servers"

i found one with 0.06 round trip delay and it works great.
[Defy Android Development] lanfearxt:
i'm running beta 6, (no nightlies for me) and i think it's pretty stable enough for long term use...meaning, even if no more updates on cm7, i will still use this ROM. i mean, it's that good, even over stock ROMs. heck, even stock 2.3 comes out, i might still be on this beta6. everything that i need to use, is usable and good enough. probably need a proper personalised ringtone setter. i hate using those free apps. problem is, using android systems settings, it cannot 'see' the mp3 on the sd card, and can only set the standard android ringtones
[Defy Android Development] Epsylon3:
the speed in 30 nighty seems not related to sdcard, but to something new in framebuffer access...

in PicMe : Failed to load native library fb_access.so
[Defy Android Development] ccav2000:
OK, will try it now. I know good ntp servers for my country, I run my own ntp daemon at home too in my Linux home server.

Cudos to Epsilon3 for the DroidSSHd, makes editing those files via Putty and nano sooooo easy!
[Defy Android Development] ccav2000:
Works is a little slow, so I took the DEFY and went out, to the middle of a small square we have here. The accuracy improved significantly.

I don't know, maybe the DEFY sucks when the signal is not so good. In such a case there is nothing anyone can do.
[Defy Android Development] ccav2000:
Oh well, if anyone has any good ideas about GPS improvement I'm all ears. For now I'll just bear with it.

Someone said that in last nightly the camera is improved?
[Defy Android Development] hailmary:
gps

i dont know about gps things.i only can read maps,so gps doesnt bother me at all.

a lot of stock SEA froyo users r complaining in my forum abt inaccuracy of the gps too.

im not sure but just maybe its w/ the defy or the default gps maps...

btw pics n cam record so vivid.its like watching private ryan in widescrreen hd.:D
[Defy Android Development] ccav2000:
@hailmary

Which lens you have? Green or Red?
[Defy Android Development] hailmary:
i have green..im on knightly 110539-0009.and as usual i wipe cache & dalvik only...

btw moto pulled back the sea fota due to bugs & it could be related to the gps things my fellas been testing for a week now here in manila.
[Defy Android Development] n0_alterNative__:
My Defy has 2100 points on Quadrant Benchmark on 1 Ghz processor. Is it real ? I'm using the last Nightly Build.
[Defy Android Development] ccav2000:
Should be. I didn't install that build, but I heard something about speed boosts. Not sure what, couldn't find the relevant git commit.
[Defy Android Development] Jefgenowitsch:
By the way, i think i have found another bug. when my phone is plugged to my computer and i restart my phone, my computer does not recognize my phone although my phone is being charged.

i only get connectivity when i unplug und plug my phone manually.

Another problem is that with long time being unplugged(mostly over night)

my device is not recognized by my computer, only after i restart my phone.

Does somebody have the same problems?
[Defy Android Development] vick33:
I tried to solve the couple remaining bugs in camera but i am not experienced enough in java but i am trying:-), the issues remain to correct:

-zoom above 4X (i can remove it, but should i? Is it works under 2.2 with lgcamera? )

-Camera freeze when changing photo to widescreen (I know what causes it but i could not figure a solution to it if someone experienced in android camera api could help me)

- Cannot change torch in widescreen mode(it is easy to correct but dont had time because i spent my time on the first two issue)

it is because the read_ahead modifications and the video codec modifications, but dont give too much credit to quadrant or any other benchmark. My spica has almost two times the cpu score of the eclair defy and still slow as Hell:-)
[Defy Android Development] ccav2000:
Zoom above 4x was reported to work in the red lens only.

As for the benching, many people say that Quadrant is obsolete. Some of them are devs, so I tend to trust them.
[Defy Android Development] urbantue:
Problems with green leds camera

Hi,

until i changes to cyangenmod 7 my camera seems to be broken. Everytime it just shows a black screen. No change after switching to the newst nighty build.

How can I enable the camera again?

:)
[Defy Android Development] ccav2000:
Try to go to Settings -> Applications, find the "Camera" app and clear its data.
[Defy Android Development] darktyroll:
or uninstall 2ndinit
[Defy Android Development] supergenio2:
hi!!!

which is the WVGA video recording for green camera (author vick33)?, because mine is red lens (I think), and will not let me record in HD, WVGA is perhaps the setting as high?

see you later.....
[Defy Android Development] ofmb:
so it did improve accuracy.. eventually

there's nothing to do - GPS signal gets distorted in an urban area.

read here:

http://blogs.agi.com/agi/?p=1779

and see here:

http://www.youtube.com/watch?v=Bcmy7j4uXls

unless you test the two devices hand to hand with same configuration and same application (GPS test) its hard to tell that "the defy's GPS sucks"

and as i side note:

there are many GPS algorithms, and even more algos to handle GPS distortion.

each one is different in fix time and accuracy even for the same input.

after all i'm very pleased with GPS right now - it gives me great results in an open space and satisfying results in urban areas.

i don't think its much better with other phones.
[Defy Android Development] Sir Flashalot:
Although I require a working phone I got cocky last night and upgraded from 3.4.3-11 / beta6 to cm7-110529-1851-NIGHTLY-Jordan.zip, did wipe data/cache before upgrading.

Videocamera:

- No HD recording on green lens, preview is in widescreen, record button does not react. Recording in High is OK.

Photocamera:

- 4x zoom is max, above it is garbled in all modes.

- FC when switching to 4M pixels (wide). "Cannot connect to camera" when reopening app. Ok after reboot.

- In 4M pixels (wide) mode, zoom goes till 6x but is stretched horizontally only.

- When switching flash from On to Auto, it stays on in daylight conditions.

Various:

- Boots in approximately 35 seconds, nice!

- 720p video playback ok.

- Call mic when using external spk is ok.

- Emergency call only and no Data connection! Switched baseband to Europe RT_3.4.2-145 and it's fine again.

- Installed AngelDeath's netherlands.zip to increase gps fix for my area. Cold start with aGPS in less than 6 secs. Similar as in beta6.

- Exact and stable gps positioning in Google Maps and Maverick on the very first fix. When trying a second time, it's Borg'ed again... Noticed this in previous builds as well. Somehow the location.cfg and/or gps.conf are altered after initial gps fix. In previous builds, I already tried to change QOS ACCURACY=50 in gps.conf to a higher treshold, but nogo.
[Defy Android Development] binodnepal:
have you tried double tapping the screen in preview?
[Defy Android Development] urbantue:
Hi, no change. Camera does not work at all. :(

Even a factory reset/wipe date -> reinstall does not change anything. :(
[Defy Android Development] Epsylon3:
New nightly 20110530-1247 :)

Fixes the FC issues in most apps... and still so fast !:)

Click on my signature to access them...

2192 in quadrant with default settings, oc profile in bootmenu disabled

PS: oups, bad clicked on urbantue Thanks button....
[Defy Android Development] urbantue:
yes, no change. Does not get any preview. :(
[Defy Android Development] stapuv:
-4x zoom for green lens, 6x zoom only for red lens

-FC when switching to 4M pixels (wide) - you have to double tapping the screen or change 5M then 4M

- green lens can't recorh hd only red

- so some are not bugs but works only for red lenses
[Defy Android Development] vjgrace:
Opera Mobile & Opera Mini FC

Hello all,

Tried nightly 052911 1851 & 053011 0009 and both have FC with opera mobile and opera mini, 052311 0638 had no such issues.

Any one else getting FC with Opera with recent nightlies?

Thanks for your time.
[Defy Android Development] Sir Flashalot:
Thanks, but I've been reading this thread since the beginning, so I'm aware these are known issues, restrictions (red lense) and the various workarounds. I'm just reporting my feedback on the nightly version.
[Defy Android Development] Jokerchris2000:
Ok so with the newest nightly (110530-1247) Navigon has no FC anymore. Ill do some testing now and report later if i find some more bugs...
[Defy Android Development] Perilla_:
Did you try wide videorecording? That works in WVGA.
[Defy Android Development] Corwinder:
Newest nightly for the 30th 1247 has fixed my Launcher Pro FC issues. Very Very fast. I like. GPS is spot on. I see I have a green lense so on that I'll wait patiently and see what happens.
[Defy Android Development] kirpeace:
can the system now be restored or there is still problem
[Defy Android Development] Epsylon3:
yes it can since yesterday.. i will not do a restore today, please confirm with lastest one... there was some littles fixes from cyanogen yesterday
[Defy Android Development] vjgrace:
Hello all,

Just to let you know, the latest nightly (110530 1247) fixed the Opera Mobile/Mini FC issue.

Thanks
[Defy Android Development] MAO2200:
Then, yesterday and immediately put THAT SHOW!

But not served and did not change the camera resolution to the photos ... now updated to the latest nightly and are also pictures and videos ... non-HD videos ...

Then the GPS, splayed position yesterday of about 100/200 meters, now wonderfully with accuracy up to 9 m. ... if they would bring in 3 / 4, tells me the exact point of evacuation morning ... I really want to do is have a clear!

Thanks to all of you who have made this miracle possible! GRAZIEEEE (thanks)

:D:D:D:D:D
[Defy Android Development] Sir Flashalot:
Is it still accurate on second cold start GPS fix?

Edit:

@Perilla_ Wide works fine indeed.
[Defy Android Development] hailmary:
@ccav2000,

Zoom above 4x was reported to work in the red lens only

****

widescreen zoom 4x+ working on mine.

i zoom on 6x & yah i took picture of my shoes just now..its working on mine--i have green lense-i see the lense in the back of my defy,its green dot in the middle.

i dont know why some say its not working?maybe my defy is different-could this be a red lense?:confused:
[Defy Android Development] bobo9900:
Can someone please share working wvga recording blurcamera.apk from the latest build?
[Defy Android Development] adi4motion:
does your phone vibrates (haptic feedback) when you unlock it/switch to silent in the latest nightly? mine doesn't
[Defy Android Development] Corwinder:
Yes, gps is consistently accurate. I do live in a small town without a lot of urban interference.

I do have another minor problem. When using TV.com to watch video the phone goes to sleep after 2 minutes. I would think there should be a setting to suspend screen timeout while applications are in the forefront or something like that. For the life of me I can't find anything other then just increasing the screen timeout.
[Defy Android Development] walter79:
cm7-110530-1247-NIGHTLY-Jordan.zip

Home-button did not work.
[Defy Android Development] Perilla_:
Green lens, 4x+ zoom "works": preview broken but photo ok. 4x+ video works.

Mine works.
[Defy Android Development] Dark_Plasma:
Neither does mine with the last two nightlys.

Sent from my lightning fast defy running CM7.....
[Defy Android Development] maniac103:
Does FM radio work for anyone with latest nightlies? I only get an infinite 'Loading FM radio. Please wait'. If I cancel it, I can set a frequency, but the headset and/or speaker stay silent.
[Defy Android Development] hailmary:
FM Radio-almost forgot that.i'll test it later.
[Defy Android Development] ccav2000:
Same here. A bit annoying, I suspect it could be something from the latest changes in the CM sources, I don't think the devs of the DEFY mod did something.
[Defy Android Development] Dark_Plasma:
There used to be a setting for it under cm settings somewhere but the setting is not there anymore. Hopefully this can be put back in.

Edit: fm works fine here

Sent from my lightning fast defy running CM7.....
[Defy Android Development] Jefgenowitsch:
FM Radio works here too!
[Defy Android Development] sunoldman:
Maybe should install kickback.
[Defy Android Development] supergenio2:
anyone can tell me something
[Defy Android Development] vick33:
HD is not WVGA. WVGA is called wide in the camera app. If you have red lens it should have worked you for a while.

Hd is still not working
[Defy Android Development] adi4motion:
kickback does a lousy job:(
[Defy Android Development] Corwinder:
FM radio works for me. I did speak too soon about Launcher Pro. It is now FC after about a minute or so into a reboot. I did start messing around more with the camera. I found that if I stay away from 4m Wide all other settings will zoom to 4 but the preview garbles after that. I can take a picture but I just don't have a preview. If I go to 4m Wide I can zoom all the way to 6x now. But then if I go back to any other mode and start sliding the zoom the preview will freeze. On 5m after 4m the camera app locks up. I can get out of it but the camera won't reload until after a reboot. lol I'm not complaining 4m wide is nice for a phone camera.
[Defy Android Development] madhuranand007:
When we expect the new beta release?? .... I m really ****ed up from nightly and miui ... please quarx release it soon .... pleaseeee
[Defy Android Development] vick33:
use the newest nightly. There are some bugs what needs to be corrected. If you want it sooner try to help coding to him.:D
[Defy Android Development] sunoldman:
Next one should be RC, so they try their best to make it perfect before publish
[Defy Android Development] Fotogravin:
With 110530-1247-NIGHTLY I don't have any problems with Sygic, Just the hd-recording (red lens) is still not working, but I can live with that. It feels really smooth right now.

If I discover any other bug, I'll report it here
[Defy Android Development] maniac103:
Does it work after cancelling the please wait popup or don't you get that popup at all?

Are you in Europe or US?
[Defy Android Development] Jefgenowitsch:
I'm from Germany. I get the popup, than I'm asked if it should scan for available stations, I click yes and than he perfectly scans and finds many stations. For me it works perfect.
[Defy Android Development] psicodelico:
This is a bug on FMRadio. Try reboot your phone and open FMRadio app again.
[Defy Android Development] Fotogravin:
Home button and FM-radio both work for me.
[Defy Android Development] maniac103:
I did that a ton of times already :(

I wonder what might be different on my power compared to yours. Does any of you have BT enabled? This is about the only thing I can think of.
[Defy Android Development] Fotogravin:
I can confirm that no bluetooth is possible while having FM-radio on and FM-radio get stuck if you try to start it with bt already on
[Defy Android Development] Corwinder:
Sorry, I'd rather see Quarx take his time and work out as many bugs as possible. When the nightlys start getting even more polished that's probably when you can expect to see the next release.
[Defy Android Development] Quarx:
Widescreen photo finally fixed:))
[Defy Android Development] Sir Flashalot:
Same here. When BT enabled (paired with or without BT headset), message "FM Radio is being launched, please wait...". Message disappears on Back button but touchscreen is inactive. Disconnecting BT headset or disabling BT on Defy does not solve this. FM scan is not possible and (of course) no sound from wired or BT headset. By rebooting it's possible to use FM Radio again, only when BT is disabled

BT cannot be enabled when FM Radio is active (no BT icon in status bar).
[Defy Android Development] Fotogravin:
I killed the FM-radio app by going to Settings-Applications-Active Services (don't know if I use the right names, have the menu in Dutch, not in English) en manually stop the FM-radio service. After that I could start it again with no problems (as long as I had bluetooth turned off ofcourse). So I didn't need to reboot the phone (saves time ;) )
[Defy Android Development] AkkiandDefy:
OMG :D

You're the Lionel Messi of Defy.

Quarx is not from the earth, too intelligent :D

Sorry for being to harsh, but upload the new beta, or maybe RC(:rolleyes::rolleyes:) as soon as possible

Please ;)
[Defy Android Development] wizwin:
Emergency calls only?

Guys,

I am using beta6 with 1-step battery fix and 100% CPU fix. It was all fine but for the past 2 days my phone is constantly going into "Emergency calls only".

I am sure about the network coverage. I did not change any settings that can possibly affect this. I tried using the baseband switcher after this issue but I am not sure which one to use and there seems to be no reason for me to change it as it was all well before. Any quick fix to this issue?

:confused:

I am in the middle of an emergency, so could not search through all the posts.

CM7 getting AI? :P
[Defy Android Development] AkkiandDefy:
At all please vote, if you didn't voted before.

They aren't leading anymore. So please vote, I'm sure Quarx would be happy, or ;)?