Database Users

I5800dtlkda

New firmware for our devices I5800DTLKDA (2.2)

jonathantng said:
New firmware for our devices I5800DTLKDA (2.2)
Click to expand...
Click to collapse
What's the difference? What's new in this ROM?
It's just a US based firmware I think.

Its for Canadian users of I5800L. Probably Latin American countries too....

Anyone know if this rom is for the 3 galaxy i5800L of Brazil, if there is any blockage in this rom is yes or any other kind, since I'm using the European Roma JPF, and I'm scared to update this with my phone and brik
was very grateful for whoever can help

Thanks Clarkkov, the rom works perfectly, improved GPS, WIFI, the speed of app, and did not change my programs do not run a hard reset. The only catch is that for anyone in Brazil there is no language PT-PT or PT-BR.

Wdconta said:
Thanks Clarkkov, the rom works perfectly, improved GPS, WIFI, the speed of app, and did not change my programs do not run a hard reset. The only catch is that for anyone in Brazil there is no language PT-PT or PT-BR.
Click to expand...
Click to collapse
Yes, the rom is fine , the menus are in english, but you can install swype beta for pt-pt
Sent from my GT-I5800D using XDA App

Hello, sorry is my question is trivial, but i tested many other roms but i can flash this one, afeter oding reboots my phone, there's a recovery mode screen saying E:Can't mount /dev/block/mmcblk0p2 and i tried 3 times, same results, so i'd like ask how you flashed correctly, thank you very much

I used this ROM in my GT-i5800L (from Vivo In Brazil) and my experience was not one of the best.
For starters, lots of the bugs I have seen in other Froyo releases are still there:
The alarm clock bug (if say it is 7:00PM and you want to set an alarm clock for the next day at 8:00AM, it automatically sets it for 8:00AM on the current day of the week, in other words it sets the alarm for 6 days and 13 hours, rather than in 13 hours) this becomes a problem because you have to manually change the days.
During a call, if you use the sensor the screen turns off, but when the screen turns back on after you apart it from your ear, the notification bar lights up green. This isn't a problematic bug, but it just shows an unfinished look and feel.
Rooting is a problem (z4Root does not work) and after rooting with SuperOneClick, the phone becomes slow, and even after installing busybox, there are noticeable differences.
GPS still takes forever to get a lock, when it actually does.
The camera can take only one photo. If you try to take a second shot without first leaving the camera, 80% of the times, the camera will lock up, show a green screen and/or force close.
The supposedly improved memory management of Froyo also doesn't become apparent. The included task manager doesn't show you running first party programs, just third party... Although clearing the memory is a bad thing for Android (you should only kill active programs if they are really slowing the phone down. Killing programs kills the battery life), you cannot do a thing to control it. The only option you are left with is wiping Level 1 and Level 2 memory, killing ALL active programs. If you want to SELECT which programs you want to kill, they have to be third-party programs.
Downloadable task managers seem to have little effect, since Froyo changes the way you can kill apps belonging to Android (first-party).
Because of the poor management, listening through Bluetooth is impossible, since the audio fades every 10 - 20 seconds because the phone neeeds to think. I first thought it was an AudioTuning issue, but then I tried launching a heavy app while playing music via BT, and the problem becomes evident.
Also, whenever I connect to bluetooth in my car, my in call volume gets dropped down to 50%. That's okay, because there would be too much noise coming from the car speakers, but when I disconnect my bluetooth, I expect my volume to be taken back up where it originally was. Eclair did not solve this, Froyo promised to solve it, but in any of the firmwares I've tried, have they actually done anything about it.
I previously had installed JPF and JPM with similar issues as listed above. By installing an American version I thought battery life would be greater, since it wouldn't have to be searching for 3G on frequencies of 3G not used in American countries. Although my battery life was better than JPF and JPM, my original firmware (streamlined with only actual useful apps and etc. - if you want to take a look at streamlining look for my post Streamlined Apps for 2.1 / 2.2) works better than any other firmware I have used (including Kyrillos and Apocalypse).
I miss the GPS button on the notification drop bar, and the Google groups in my contacts. But rather than that, I see no way where Froyo beats Eclair...
Mind you I don't use tethering, VPN, do not play heavy games (as I feel consoles and computers are there for that kind of thing - I just have light games installed like Air Control, Zuma, Labyrinth, etc.. to pass the time), turn off my wifi and bluetooth when not in use, leave my brightness to a minimum unless I can't see (then i turn brightness up), but have 3G running all the time, bluetooth whenever I am in the car, and Wi-Fi whenever I need to use the web and am near a known wi-fi antenna.
Battery Life (with indications above):
I5800LVIJG7 (2.1 Vivo) - 60 Hours
I5800LVIJG8 (2.1 TICO?) - 56 Hours
I5800DTLKDA (2.2 Free) - 35 Hours
JPM /JPF / Kyrillos / Apocalypse / Lestatious - 18 to 25 Hours
Hope that helps...
My advice.. stick with what you have...

Good morning, I tried other rom tb's but found this the best, my battery lasts around 2 days using wifi and 3G, I liked this rom, my GPS was fast after I turn on my GPS the following, the squeegee GPSFIXS with 1 minute and it fixed my location from GPS point of 100% with 3 to 18 meters of accuracy.
I would like to return to the rom VIVO because I believe that new skirt rom soon

I Flashed this rom, but the apks: gpssetup2 and fmradio aren't in the rom.
I copied fmradio.apk from I5800XXJPS and worked, but the gpssetup.apk didn't work. Because this my GPS don't work.
Anyone help me to solve my GPS problem in this rom?

Cyanogen battery drain HELP !!

Hello. I used cyanogen mod in the past on my desire hd, then switched to rcmixhd, then back to cyanogen (newer release). I noticed first of all that the battery lasts really shorter time. I don't know why, but in the night it goes from 60 to 15% without using anything (no 3g, no wifi, no applications, no alarm), i just leave the telephone on. It hasn't happened to me before.
I flashed a new radio, I will see what happens, but can the radio make a difference in the battery related problem?
Apart from this, i am happy with cyanogen.
One rom related question: is it possible to change the incoming call layout? I am very used to the possibility of 'SILENTING' the call. Let's say someone calls, I want to have the possibility to make the phone NOT ring while still NOT refusing the call. On this rom I only have 2 buttons: accept and decline. No 'silent ringtone' available while the phone rings, which is different to refusing the call. I just want to keep the incoming call without the ringtone, after the call starts...i think you understand what i mean, it is a common function in every rom I had.
And also: I tried the game 'backstab HD'. It runs really with poor framerate. Is it normal? It has good graphics ok, but I don't think it's normal for a game built for phones to go that slow. Modern combat goes very smooth...even reckless racing HD now goes smoother than before. Backstab is almost unplayable. I think I could do something with chainfire 3d ?

rogermorse said:
One rom related question: is it possible to change the incoming call layout? I am very used to the possibility of 'SILENTING' the call. Let's say someone calls, I want to have the possibility to make the phone NOT ring while still NOT refusing the call. On this rom I only have 2 buttons: accept and decline. No 'silent ringtone' available while the phone rings, which is different to refusing the call. I just want to keep the incoming call without the ringtone, after the call starts...i think you understand what i mean, it is a common function in every rom I had.
Click to expand...
Click to collapse
Volume down should silence the ring/vibrate.

tonight battery went from 70% to 2% (from 3.30 a.m. to 10 a.m.). I find it impossible to use the phone like this.
How can I fix this battery problem? Last time I used cyanogen the battery could last up to 3 days with normal use. With the time the ROM should get better, not worse....I am searching for a solution, many people have this problem and no one knows how to fix it.

rogermorse said:
I flashed a new radio, I will see what happens, but can the radio make a difference in the battery related problem?
Click to expand...
Click to collapse
Hi !
Check out the radio threads, and see the setups from the other guys.
I had heavy battery drain with different radios. The last radio from cyanogen
( running alienmind v1.99 ) works great now.
Just need to test everything and need to find the best setup for you

Now, one of better think is to make a full charge of your battery, device turned off.
when you reboot your device(at 100%), go in CWM=>advanced=>clean/wipe battery stat.
Do it two or three time and see...
if no result you can instal Battery History for GB
Look if something drain anormaly your battery.
If no result, change ROM
If no result, change your dead battery.
And read this guide

i did the reset of the battery stats today, things may be better. I will also flash another radio to try everything. If not, I really don't know, i may have to change rom although i was happy with cyanogen the first time.

Just backup your old rom and flash (wipe) the newest from cyanogen... and see yourself.
If the battery drain is still there ( i hope not )
I had only problems with cyanogen when i customized it ( other radios, kernels and widgets )

so which radio is the best for the latest cm7? I have the Telus version if that makes a difference. thx

Yeah I was getting pretty severe battery drains too, but then I updated my radio and RIL and now it's significantly better. Here is a guide to update your radio:
http://forum.xda-developers.com/showthread.php?t=877295&highlight=radio
After that I updated my RIL using CWM. Just go to Download ROM -> gtg465x -> RIL Flasher.

I'm currently using Radio_12.54.60.25_26.09.04.11_M2 with AlienMinds CM 7.1 v 1.9.9 with great success. Great battery life and smooth operation.
Duncan

It really does take 30 minutes to flash Synergy RC2 + God Mode

With the understanding that RC2 will be superseded by RLS1 very very shortly, I thought I would share my godmode "upgrade" experience from yesterday anyway:
For me, the elapsed time between booting into Amon Ra and finally getting a booted OS (let's define that as the earliest you can pull up the lock ring and get to a homsecreen, even if it is very laggy still) :
20 minutes grand total.
The total time before I could launch an app or actually use the phone in a meaningful way was more like 30 minutes.
Total time before the pain of initial lagginess no longer called attention to itself (ie, you could use the phone without the thought of "damn this is slow" intruding in your mind) : hours.
The long delays during the install process happen at times that are different from what I expected
Flashing the actual zip while in Amon Ra:
8 minutes total. Progress bar seems to hang on around the 50% mark (right under the "u" in Virus") for at least half the time, then the bar fills in to 100% suddenly, then a long wait at 100%, then back to the interactive Amon Ra interface.
At this point Rosie 3.0 carousel "non-landscape" people such as myself flash the appropriate mod ( I did the one with Rosie 3.0 widgets). Very brief ( a few seconds to navigate to your zip, a few seconds to flash).
What happens after you select "Reboot now" in Amon Ra?
First, the "white screen with black 'htc EVO 4G' text" (Note this is different from the "white screen with green 'htc' logo" you get later (and indeed any time Sense reloads, whether due to crashes, first boot, reloading after titanium activity etc)).
This lasted only 3 minutes.
Then the glowing green "SYNEAGY AOM" ( <-- not a typo, look carefully at boot animation ;> ) throbbing-synapse-loop boot animation.
This lasted 9 minutes. Sometimes the synapses throbbed very slowly.
Then finally a brief glimpse of lock ring on top of wallpaper. No shortcut icons visible. If you don't touch phone, the screen promptly goes to sleep. Which is fine. It could probably use a little quiet time at this point.
(If you just touch the power button but don't actually mess with lock ring it's amusing to watch what time it is. First it will be something like UTC time, totally off from your local time unless you're actually in England. Then a while later it will spontaneously change to local time, except in 24-hour format (eg 21:57) . Then finally it will revert to 12-hour format (eg 9:57). Takes several minutes.)
Finally I unlocked it and the first thing I was greeted with was a modal dialog saying "Process com.android.phone is not responding...Force Close / Wait". I chose wait and immediately was shown the "white screen with green 'htc' logo" for a good five minutes of totally non-interactive wait time.
I left the phone alone during this time and eventually it finished doing what it was doing and it fell back asleep. When I woke it up, I was placed directly in the Setup Wizard app. Interestingly, the first screen of the setup wizard has a 'back' button. Not feeling like signing in to anything just yet I hit 'back'. Again came the "white screen with green 'htc' logo", then a desktop with a dialog just saying "Loading" for yet another minute.
At last a real homsecreen appears (now with the familiar constellation of six icons, and, again, no clock/weather widget), the tips widget throws up a balloon with its first tip, and finally you can actually use the phone.
This would be around the 30 minute point since the flashing process started.
There are times during this initial break-in stage where it seems the phone is almost unresponsive. Touches may *begin* to get responded to after a five second lag or more. The response itself can take 5 seconds more to do something simple like simply redrawing a button with its highlight color after a button press, let alone performing the requested action.
That phone / wait dialog comes up a lot. For instance I just saw it again today when someone actually called me. I chose wait and then answered the call normally.)
Ominously, I also saw a dialog later concerning "android.process.media" which concerns me because the point of god mode is to change the way the filesystem works for basic I/O functions.
Still haven't ever signed in to my main google account yet. Seeing how far I can take this before I do. I suspect as soon as I sign in it will start downloading all my apps from the Market. Which force closed on me by the way when I was doing something totally unrelated (just poking around Spare Parts I believe it was).
Also the first time I tried all this the internet browser app simply did not work right out of the box. Force closed every time. (I restored app+data for just the browser app from my titanium backup I made (while running RC2 non god mode) prior to the install and got my browser back. That didn't give me warm and fuzzy feelings.)
Later I repeated the entire install procedure from scratch and did not experience market FC's or internet browser FC's. Not sure why the second time would be different.
Note I was not connected to AC power during any flashing or initial boot up.
For those playing along at home, you may be curious to know things like what kind of phone do I have, how did I prepare to flash, and what was the exact sequence of steps during wiping / flashing?
OG Evo HW 004, original SD card ( I believe that means 8 GB class 2), never toyed with any kind of partitioning. Previous ROMS have all worked fine with the SD card which has the usual folders full of pictures, nandroids, titanium, folders created by previous ROMs including Synergy, etc.
Latest radios, PRI, PRL, GPS works, 4G keys happy, never had any drama.
Before flashing God Mode I was already running Synergy RC2, and once I was ready to say good bye, I did a nandroid backup, then rebooted, connected to a PC and offloaded any new camera pictures, some recent nandroids and uploaded the ROM image ( I did check the md5) and the Rosie mod I intended to use (dkdude, not fdb) . Then ran titanium, backing up all user plus system apps, then finally did one last quadrant test (just under 1000), took a deep breath, and rebooted into Amon Ra 2.3 .
From there I did these wipes in this order:
rotation
battery
dalvik
cache
data
factory reset
Yes I realize many of these are redundant. Then, to be *really* redundant, I left wipe mode and went into flash zip mode and flashed calkulins format all tool. I believe this also wipes boot amongst other things.
So now at this stage the phone is fairly re-virginized. The only thing I haven't touched is the SD card which has the zips I want to flash.
Now I flash the actual synergy RC2 god mode zip (as described at the very top), then the rosie mod, getting no errors for either one, and then without further ado selected reboot now, which brings us back to the firstboot behavior chronicled above.
Edit: I did restore quadrant and got 1600 on my first run: make of that what you will.

[Reserved for updates on 4G experience, bluetooth, gapps, general usability etc...]
Quick update: I did successfully test 4G, WiFi, bluetooth, and GPS.
I finally signed in to Google and sure enough market downloaded all my apps. This may be a Synergy thing- Synergy also seems to remember things from previous installs despite the elaborate wiping regime described above, such as the password to my WiFi access point some search term history, maybe a few other settings.
Anyways, during the download and install of a moderately small number of market apps (I have like 15, all free) the phone was effectively unusable. Almost unresponsive. Finally a half hour after the install activity was no longer apparent, things seemed to settle down and the phone gradually seemed to become normal again.
Quadrant scores were originally as low as 1200 something. Then got it up in the 1400's, then finally i have seen several in a row in the mid-1500's. Again, for reference, I consistently got around 1000 with vanilla RC2 (and the same hardware gave me 1200 with CyanogenMod 7.1 RC1 for you AOSP fans out there).

And this is supposed to be an upgrade???

The party line is *once the phone has had time to settle in* things get a little faster in real world experience. I am in fact beginning to see the promised behavior now, 12 hours after install (including maybe 4 hours of heavy usage)
Certainly the improvements to the benchmark scores are immediate, but we can all agree actual 'driveability' is more important.
So far, I will say it's looking better with each passing hour.
As an example, the simple spinning carousel action (remember I'm doing the Rosie 3.0 carousel mod) under RC2-non-GM was clearly straining the limits of what the Evo could smoothly render. With god mode, it's clearly different, faster and smoother.
Here's the feeling I get: every time you do something for the *first time*, let's say the first time you launch a particular app, activate a certain part of the Rosie UI, get a new dialog box, there's a punishing lag. The *next time* you launch that app, or swipe that tab, or experience that same condition, it's faster. Indeed perhaps faster than it ever was in plain old RC2.
But the make-or-break thing will always be stability, or should I say predictability: days from now, if I still see a lot of Force Close's, or if I am still experiencing unexpected moments of slowness while it "learns" how to do something (and you know how Murphy's law works- it will always happen at just that moment where you can't afford to be surprised by a mysterious delay) - well, it may be back to regular Synergy. Hard to say. I'm a patient person. I intend to give this a good long audition.

When I Flashed the Alpha it took forever, but yes RC2+ was a very pleasant flash by comparison, just flash ROM - flash mount zip - flash carousel + widgets - flash unmount zip. then Im using link2sd and TB. Does anyone know of another a2sd gui that is good? want to prepare for RLS1

I had a similar experience giving rc2+ a try. It was borderline useless on my phone for whatever reasons. Went from rc2 to + after a nandroid backup and did a wipe of dalvik and cache. After about 6 hours of usage I said screw it and restored back to my nandroid backup which is blisteringly fast. The "seat test" on the phone wasn't great at all but the quadrant resulted in test results in the 1700-1800 range which is awesome. I too am on the stock class 2 card and I planned on buying a new card so maybe the results will be better with a new card?

TruthAEE said:
When I Flashed the Alpha it took forever, but yes RC2+ was a very pleasant flash by comparison, just flash ROM - flash mount zip - flash carousel + widgets - flash unmount zip. then Im using link2sd and TB. Does anyone know of another a2sd gui that is good? want to prepare for RLS1
Click to expand...
Click to collapse
The main Synergy thread is full of discussions on a2sd stuff.
Interesting that you flashed the rosie mod using the mount / unmount strategy. I chose to use a rosie mod that had specifically been re-written for godmode. I suppose you end up at the same place either way.

I wonder how it would run on a 32gb class 10.
Sent from my locked tight OG EVO using XDA Premium App

I have seen a lot of wildy varying reports on upgrading your SD card. When it works, it works. It's awesome. But there are also reports of even "class 10" cards that did not improve performance at all. Could come down to who the SD card manufacturer is.
If you tweak everything just right (note most people say to leave dalvik in internal memory regardless) with a swap partitioin, ext3 paritition, a2sd, then maybe one of the new custom kernels that have just come out, and maybe even apply the v6 super charger memory management trick, I bet this ROM could fly, benchmark or no benchmark.

[TIP] FM Radio users one setting could cause drastic battery usage.

First the tip: Don't use the "Show Station ID" option, it causes a massive battery usage.
Here are some numbers, with it turned on 4 hours of uninterrupted radio listening drains 36% of my battery. With it turned off the same 4 hours only drains 20% of my battery.
This is caused because with it turned on the phone never goes to sleep when the screen is off. When it is off the phone actually goes into deep sleep will still playing music which causes the drastic difference.
My numbers are based on 40 hours a week listening for 5 months of Station ID being turned on without thinking about it and getting a consistent 36%/4hr daily
Then I did my only factory reset when going to a ICS rom a couple weeks ago and not thinking to set it I started only losing 20%/4hr and noticed I was spending time in deep sleep.
It's great leaving work after a 8 hour day with a extra ~30% battery then I have been used to.

Actually that's not an accurate comparison seeing that you've switched roms.
Try to compare it now on your new rom so that the comparison is done on same roms.
But thanks for the info anyway.

I think this may be due to the HUGE number of messages written to logs when RDS is enabled. I see this with my FM app using the RDS in my app's Samsung FM API mode, and there's not too much I can do about it in that mode.
====
BTW, I very much need people with S2's to help me get my app working on stock or stock derived ROMs on which the stock FM app works. It works fine on Galaxy S for a while and probably just needs a tweak or 2. See my post here and respond via PM or on my thread, since it's Off Topic to this thread.
Except that... perhaps my app can use less power when in background or screen offm since it can turn the RDS off then.

bpivk said:
Actually that's not an accurate comparison seeing that you've switched roms.
Try to compare it now on your new rom so that the comparison is done on same roms.
But thanks for the info anyway.
Click to expand...
Click to collapse
I did a quick 1 hour test with it on and the numbers still match up. My phone lost 9/hr which does equal 36/4hr.

shadowofdarkness said:
I did a quick 1 hour test with it on and the numbers still match up. My phone lost 9/hr which does equal 36/4hr.
Click to expand...
Click to collapse
I'll run a test on my Galaxy S and I'd bet the same thing happens. I think a dozen or more log messages every second can do the battery in faster.
For you or anyone else looking to test my app, there's not much to it:
Feb 26 release on the Market: https://market.android.com/details?id=com.mikersmicros.fm
Possibly better Feb 28 release: http://www.mediafire.com/file/i5654nm9vzd9d9m/Spirit_FM_Radio_v120228.apk
Just ensure a wired headset is plugged in, install the app and run. If you are rooted you should deny SU when it starts. At the Intro screen, press "Disable".
Hopefully, it will "just work" at that point.
NOTE: I just realized now that if you give my app SU, it will not try the Samsung FM API, it will go straight to the low level mode which gives no audio on the GS2. So set Menu->Settings->Debug->FM API to "OEM Proprietary" to force use of the Samsung FM API. If this API fails, I think the app will fall back to the low level mode. That can be prevented by setting Debug->FM Chip to "TI" and if the OEM API fails, then power up will fail.
Working or not, please give SU to my app, restart the app and send me a debug log with Menu->Help->EM Logs. After a few seconds. enter "GS2" and/or any useful phone or ROM etc. information in the email text and press send.
Remember, this test request is for stock or stock derived ROMs that can run the stock FM app only.
My app has been running in a "low level device driver mode" for over 6 months now on rooted GS2s, but without audio, except I think on the MIUI ROM which supports the CyananogenMod audio method. I need no testing for this mode, unless you know how to enable the FM audio or want to try the different Audio Methods to see if any magically work.

[Q] Freeze and reboot

Hello everbody,
bought 2 weeks ago the Nexus 4 16GB and I'm very happy with it.
But i have the problem, that the device restarts when it is under load, means i play or watch something what needs
the full power of the CPU and GPU.
It happens a lot when i play Iron Man 3 The Official Game or Dead Trigger.
Than the device freezes, can't kill the app or even lock the screen and after 10~ seconds it reboots itself.
Active Wifi, Bluetooth, 3G or not doesn't make any difference.
The only strange thing is, what i discovered after a few crashes, is that the battery gauge stands still before the crash and after the reboot the gauge drops to it assumed level.
Screenshot as attachment.
System: Android 4.3 Stock (with this last mini patch from last week)
Does anyone have a idea how i can fix this?
I tried, to charge the battery while android is off and to turn android at 100% on, but this doesn't help.
Sincerely,
GTrash81

GTrash81 said:
Hello everbody,
bought 2 weeks ago the Nexus 4 16GB and I'm very happy with it.
But i have the problem, that the device restarts when it is under load, means i play or watch something what needs
the full power of the CPU and GPU.
It happens a lot when i play Iron Man 3 The Official Game or Dead Trigger.
Than the device freezes, can't kill the app or even lock the screen and after 10~ seconds it reboots itself.
Active Wifi, Bluetooth, 3G or not doesn't make any difference.
The only strange thing is, what i discovered after a few crashes, is that the battery gauge stands still before the crash and after the reboot the gauge drops to it assumed level.
Screenshot as attachment.
System: Android 4.3 Stock (with this last mini patch from last week)
Does anyone have a idea how i can fix this?
I tried, to charge the battery while android is off and to turn android at 100% on, but this doesn't help.
Sincerely,
GTrash81
Click to expand...
Click to collapse
Did you undervolt the CPU?

If this is happening without rooting/etc... then I would definitely get a replacement. It sounds like the processor is overheating and causing a reboot rather than throttling.

Today i checked if the device is getting too hot.
But after 2 minutes playing Iron Man, by 9°C outside (i was on the way to the city, waiting for the train), it rebooted.
So i started the game, deactivated the display and put it on the table. After 4 hours i checked the game and played over 10 minutes without a crash.
So what i think is, that these two don't like Trim (most new feature with 4.3) or the are badly programmed and must reload/refresh objects while playing and Trim must work to clear temporary files.
And they are badly programmed, because i red at the developers page, that a few other people have the same problems.
So excuse me for wasting your time. But hey, to err is human.
Sincerely,
GTrahs81