[Q] Battery problem (complicated - please help!) - Desire Q&A, Help & Troubleshooting

Hello!
My Desire is since around 2 years back in my father's possession after being bought on release day. The battery is original and has never been replaced.
Lately his phone has been turning off at 36% battery remaining. Upon booting, the battery shows 0% charge, and charging it to 100% causes it to turn off again next time it hits around 36%. I suspect this is because the battery is very old now and has lost its charge.
I have read the very good thread on battery calibration using sense/non-sense kernels with the Nexus One Battery Calibrator app (thread here: http://forum.xda-developers.com/showpost.php?p=24599586) but this is where my problem is.
The Desire is running the SuperNova 2.4.0.1 ROM (as noted in Settings - About Software) using the kernel "2.6.35.10_basekernel[email protected] #18 Thu Feb 2 10:50:39 UTC 2012".
The phone is running the ROM to gain 2GB internal memory (DATA2SD) using a 16GB class 10 card, partitionen to Fat32 + EXT4.
According to the battery calibration thread linked above, I need to use a supported kernel for the Nexus One Battery Calibrator app. I tried running the app, but the fields were empty (meaning I am not running a supported kernel). It appears that I am running a Droidzone kernel, though. So I don't quite understand why it won't work.
At the same time, reading on Droidzone's SuperNova site, it says that if you install a different kernel and it isn't supported for the SuperNova ROM, bootloops could happen. And once bootloops happen on a DATA2SD rom, like the one my father's Desire is currently running, the Data partition becomes corrupt and you have to start from scratch with your phone and its internal memory. This is something I DO NOT WANT to happen.
My questions are:
1. Given the ROM and Kernel my father's Desire is currently running, what is the easiest way to attain a battery calibration without risking corrupting data partitions? This is because apparently the kernel his phone is using is not supported for the Nexus One Battery Calibrator app, and I need to change to another supported kernel.
2. How do I backup the MicroSD card COMPLETELY, as in keeping the partition layout and ALL data as it is on both the FAT32 and EXT4 partitions, ALONG with backing up the rom? I assume a nandroid does not back up the EXT4 partition?
I understand that just buying a new battery solves the problem easily, but original HTC batteries for the Desire are hard to come by here as they are all out of stock, so a calibration is the only viable option at the moment. As long as the phone dies when it corresponds to 0% on the display and not 40%!!
This is really important for me since his phone keeps dying between 36%, and yesterday evening it even died at 40%.
Thanks!

I have an answer for your second question.
You could backup the whole card using linux since it'll see both the fat32 and ext4 partition, whereas windows won't.
Also in 4ext recovery, doing a nandroid backup will backup your ext partition.
Sent from my HTC Desire using xda app-developers app

chromium96 said:
I have an answer for your second question.
You could backup the whole card using linux since it'll see both the fat32 and ext4 partition, whereas windows won't.
Also in 4ext recovery, doing a nandroid backup will backup your ext partition.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Thank you for your reply.
So basically if I have 4EXT reovery, doing a normal nandroid will backup my rom + data + ext4 partition? Luckily the phone is running 4EXT recovery Touch.
What procedure do I do to backup the Ext4 partition as well? Is it just "Backup" or do I go into "Advanced Backup" ?

Just doing a normal backup will backup everything including your ext partition as well. Advanced backup allows you to only backup certain aspects (ex: sd-ext, system, data, etc....)
So its fine to do just a normal backup. Btw that won't backup your fat32 partition, so u should just copy that onto a PC.
Sent from my HTC Desire using xda app-developers app

chromium96 said:
Just doing a normal backup will backup everything including your ext partition as well. Advanced backup allows you to only backup certain aspects (ex: sd-ext, system, data, etc....)
So its fine to do just a normal backup. Btw that won't backup your fat32 partition, so u should just copy that onto a PC.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I just installed the latest CM10.1 JellyBean 4.2.2 by VJ and starting the calibration app all the values show up. Does this mean I can still calibrate the battery or does it only work for Gingerbread/sense roms?

Related

Having trouble with EXT3 partition

Recently I've had problems with my sd-ext partition. When I try to backup(with CWM 3.0.0.5) my current rom, then at the backup process it doesn't write 'backing sd-ext' and when trying to restore it says 'sd-ext image not found skipping'.
I tried installing CM7 and a few other roms skipping backup, at first install it didn't read my SD card at all, second installing SD worked, but Titanium Backup didn't read the partition and all apps were installing on internal memory.
Right now I'm using a Sense 2.1+3.0 rom and everything is working good, my Desire is S-ON if it matters something.
Thanks in advance.
Check the partition in gparted
Sent from my HTC Desire using XDA App
I did, even formatted my entire SD card and redid fat32 partition and ext3.
Wipe, reformat and titanium restore?
Sent from my HTC Desire using XDA App
the 3.0.0.5 is well know to not backup the sdext
(I also think its the unique CWM with that bug..so i dont know why u using that)
use the latest 5.0.2.0...seems to work fine
I have been using this version for a while and didn't have this problem so far.
This bug only happened in the last 2 weeks or so.
And what do you think about the problem with CM7? that is not reading the sd-ext and sometimes not that sd card at all?

[Q] How to backup SDcard with stardust data2SD installed

Hi,
I've just this weekend flashed my HTC Desire with stardust ROM with data2SD.
Love it, got 2GB for apps now
But my concern, if the SDcard dies on me, the phone will not boot.
So i need to backup the SDcard (at least the EXT4 partitions i think)
I looked around on this forum and found 2 solutions:
1. Nandroid backup
2. 4EXTrecovery tool
And myself, i think a full backup in a PC with partitionmagic (partitions and full card backup) will also do the trick.
So my question: What is the best way to safely backup my SDcard, so in case of a crash, i can quickly swap it for a working version ?
I am also thinking about upgrading to a higher class SDcard for speed. so this will be an nice test to see what works.
oh, i am also S-OFF in my device.
Thanks.
optiloc said:
I've just this weekend flashed my HTC Desire with stardust ROM with data2SD.
Love it, got 2GB for apps now
Click to expand...
Click to collapse
Umm, Stardust? You mean Starburst?
I do it with nandroid backups. I backup my rom and then do occasional backups of fat32 contents to my pc.
Oeps, Yes i mean starburst
Thanks for your answer, so nadroid als backs up EXT4 partitions.
optiloc said:
so nadroid als backs up EXT4 partitions.
Click to expand...
Click to collapse
Yeah, it backs up Boot, Data, System, Cache and SD-Ext
Sent from my HTC Desire using XDA App

Sd-ext and classes

So I've been using Oxygen based roms for a while and they're all great and fast but I've gotten tired of the low internal memory. The thread for mildwild 4.4 has people saying its the fastest desire rom out there and comes with apps and data to ext by default. I installed the rom and its great, quick,and pretty. But when I started installing apps I noticed that just about all of them hang and bring up the wait/force close screen. They all respond if I wait but it takes a while. So my question is, is this being caused by my 16gb class-4 SD card? 4mbps seems fast enough to me though. I formatted the card through recovery with 1gb ext and 128mb swap.
Sent from my HTC Desire using xda app-developers app
mine's class 4, runs fine for me
plenty of posts in that thread and in general about partitioning properly: should be done with gparted or 4ext recovery only, and you don't need swap (which could be the cause of the freezes)
my recommendation would be to start from scratch again so you get a clean, fresh install. or you could wait til Mildwild releases his 'final' 4.5.0 just around the corner.
- backup sd card
- repartition from scratch as instructed
- restore sd card
- titanium backup all apps
- nandroid backup
- switch to cm7r2 hboot if you haven't already (requires s-off, search for guides)
- full wipe and reinstall rom again, enable sd-ext as in first post.
- restore apps

Recovery recommendations?

Hi.
Ever since ive rooted my desire ive been using clockworkmod recovery and I'm kind of getting bored of it. Don't get me wrong, its stable and Its never given me any problems, but i change want some change lol.
Does anyone have any recommendations for recoveries? I'm thinking of switching to either cwm touch, 4ext, or twrp.
Also when I switch, do I need to somehow delete my current recovery, or is it OK to just flash it through fastboot without deleting the old one?
Thanks
Sent from my HTC Desire using xda app-developers app
4ext recovery is highly regarded around here, it's good for partitioning sd card properly among other things. see my sig, you can install it through the 4ext app.
to change recoveries you need s-off. when you change, it automatically overwrite the previous one. i think it's only possible to have only one recovery at a time (you only need one working one!)
4ext all the way. Best for Desire.
Sent from my HTC Desire using xda premium
4Ext
I've recently switched from Clockworkmod to 4Ext and have found it quite good.
4Ext has tons of options and can be themed, the only problem I've had with it is the occasional issue where when you boot into recovery it comes up as read-only on /system.
This issue is easily resolved by deleting the 4Ext folder off your SD-Card and rebooting into recovery.
Apart from that - it's rock solid and much nicer to use than Clockworkmod....
thanks guys,
i just flashed it and its pretty cool.
I noticed that when i went to info it showed my ext partition as ext2, when i am sure that i partitioned it as ext4(using gparted)
Anyone else have this problem?
chromium96 said:
thanks guys,
i just flashed it and its pretty cool.
I noticed that when i went to info it showed my ext partition as ext2, when i am sure that i partitioned it as ext4(using gparted)
Anyone else have this problem?
Click to expand...
Click to collapse
that's strange, not seen that before. you can backup your sd card to PC, then repartition from scratch as ext4. i've converted ext3 to ext4 before using 4EXT, don't think it can do ext2 to ext4?
you can't restore a backup to a different file type afaik. in other words, if you have apps on ext2 at the moment, don't think they'll be happy if they're restored to ext4.
if you're flashing a brand new rom, not really a problem, you'll need to full wipe anyway, so you'll have a fresh new ext4 partition to fill.
eddiehk6 said:
that's strange, not seen that before. you can backup your sd card to PC, then repartition from scratch as ext4. i've converted ext3 to ext4 before using 4EXT, don't think it can do ext2 to ext4?
you can't restore a backup to a different file type afaik. in other words, if you have apps on ext2 at the moment, don't think they'll be happy if they're restored to ext4.
if you're flashing a brand new rom, not really a problem, you'll need to full wipe anyway, so you'll have a fresh new ext4 partition to fill.
Click to expand...
Click to collapse
yeah its weird. I think i'll just leave it for now as it doesnt seem to be causing any issues.
Also i got this message on the second boot into recovery saying that i changed by hboot (even though i didnt) and that i should wipe my system partition. I decided not to, and my rom booted properly, so is that message normal?
One more thing, when i boot into recovery it takes about 15 seconds to prepare the boot. Is this normal too?
15 seconds isn't normal....
That sounds like the read-only /system partition message that I've got a few times..
Resolved by deleting the 4EXT folder from SD-CARD and it was fine on the next boot into recovery. (only 2 or 3 seconds)
Thanks that fixed it.
Sent from my HTC Desire using xda app-developers app

[Q] EXT-4 gone from sd after install of HTC Desire PARANOIDANDROID Woh 4.2.2

Hi There,
First off, this is my second time installing a custom ROM and I had someone else Root this phone but I used revolutionary to S-Off. I haven't installed a custom kernel and it's running clockworkmod 2.5.07.
I flashed and installed PARANOIDANDROID Woh 4.2.2 -------------------------------------->[v. 3.10b2/7th/March/2013] as per the instructions. Before starting I formatted the microsd card to 512mb of EXT4 with remaining 6.whatever Gig's of Fat32 (I used Minitool Partition Wizard on Win 7). Both were set as primary, while Fat32 was set to active, EXT4 was set to none (didn't think it made a difference?).
Everything installed fine, however, I first noticed issue when i went to run the terminal script for a2sd and it said it was read only (as attached). I tried to change permission to read/write and that didn't work. Then I realized after mounting USB storage connecting to Win 7 and opening Minitool Partition (because sd wouldn't show in My Computer) that all that was left on the micro sd was the FAT32 partition and nothing else.
So where do I go from here? I haven't added any Google account yet or did much else because there is only 14.65MB on internal now and I obviously can't send anything to sd and although I thought GAPPS went to sd in some form I guess not.
Can I recreate the EXT4 and push anything that was originally supposed to be on that partition onto it and then start installing apps there?... or do I need to repartition and reflash everything?
Also if I need to reflash, how can I ensure the same thing doesn't happen with the micro sd?
CWM wasn't formatting when I was trying to partition from Cyanogenmod 7 running Gingerbread (although then I read that CWM has bugs and could patition NAND and brick phone) so Minitool was my only sort of n00b option despite that I was having some issues but it seemed to be all fine before flashing 4.2.2.
Hopefully the attached photos will provide any further info you need to help.
Truly appreciate your help! This is my GF's Desire and I've been in the dog house playing with it all week (Cyanmod 7 was killing battery and was buggy, even stable version).
Thanks in advance once again!
** UPDATE ***
I just used my SD adapter directly into Win 7 and it's showing both partitions in Minitool and the Fat32 is available in My Computer showing music folders etc. However, the script for A2sd still never worked in Terminal Emulator saying "sh: can't create N: read-only file system"
So it appears the partition and the data is there and available but does the above message mean I can't send apps to the sd because it's read only?
Thanks again :S
Well one of your mistakes may have been using mini tool partition wizard. Many users have reported it's unreliability, and i've also had bad experiences with it in the past.
I would recommend using gparted to delete all partitions, and then using it to format the whole card to fat32.
Then install 4ext recovery instead of cwm, and use that create the ext4 partition.
If you need help on installing+using 4ext to create the sd-ext partition check out this guide
Finally do a full wipe, reflash the ROM, and activate a2sd through terminal emulator using:
Code:
su
a2sd install
y
n
y
Sent from my HTC Desire using xda app-developers app
chromium96 said:
Well one of your mistakes may have been using mini tool partition wizard. Many users have reported it's unreliability, and i've also had bad experiences with it in the past.
I would recommend using gparted to delete all partitions, and then using it to format the whole card to fat32.
Then install 4ext recovery instead of cwm, and use that create the ext4 partition.
If you need help on installing+using 4ext to create the sd-ext partition check out this guide
Finally do a full wipe, reflash the ROM, and activate a2sd through terminal emulator using:
Code:
su
a2sd install
y
n
y
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Actually, I just ran your terminal codes above and that worked without reformatting or flashing!! It moved something like 94 or 96 apps and now shows 139 MB of internal storage!! Wow, I'm sooo excited. Imagine a n00b installing the latest version of Android on what is basically the original Android flagship HTC Desire/Nexus One!
BTW Should the developer maybe update with your script above vs the one listed which didn't work for me?
You guys rock!
I will start using GParted though and I assume using the liveimage USB would be best for me.
Now, I have to decide if I want to root my S3. I have 6 months left of my 1 year warranty so that's the only reason I've been debating it. Although most people say they've never heard Samsung not doing hardware repair just because a device is rooted. That sound about right?
Thanks Again!! So excited I'll end up using the old desire more than my S3!! lol
Gdroid1 said:
Actually, I just ran your terminal codes above and that worked without reformatting or flashing!! It moved something like 94 or 96 apps and now shows 139 MB of internal storage!! Wow, I'm sooo excited. Imagine a n00b installing the latest version of Android on what is basically the original Android flagship HTC Desire/Nexus One!
BTW Should the developer maybe update with your script above vs the one listed which didn't work for me?
You guys rock!
I will start using GParted though and I assume using the liveimage USB would be best for me.
Now, I have to decide if I want to root my S3. I have 6 months left of my 1 year warranty so that's the only reason I've been debating it. Although most people say they've never heard Samsung not doing hardware repair just because a device is rooted. That sound about right?
Thanks Again!! So excited I'll end up using the old desire more than my S3!! lol
Click to expand...
Click to collapse
lol no problem. You should root the s3. I just did it for my friends using a guide that doesnt trip the flash counter, therefore your warranty isnt voided. Press thanks if i helped
chromium96 said:
lol no problem. You should root the s3. I just did it for my friends using a guide that doesnt trip the flash counter, therefore your warranty isnt voided. Press thanks if i helped
Click to expand...
Click to collapse
Despite the fact that it's working now, should I indeed start from scratch before she's gets too comfortable with this? Flash recommended recovery and reformat sd and reflash everything? (since I originally formatted with Minitool)
BTW it appears that when we install apps will they appear to initially go to internal but after reboot they move to sd, is this actually what is happening and we should always reboot after installs and updates? I just installed about 8 apps and the internal shows it's down to 39mb but then upon reboot it's back up to 76.46 (Originally at 139 but I assume it's all app data consuming it).
Do you recommend anything to occasionally clear app data to ensure there is always space?
For the S3 I would love it if you provided a link to root without tripping the flash counter! Gesh, I love Android more and more everyday (never an issue without solution)... this community rocks!
Gdroid1 said:
Despite the fact that it's working now, should I indeed start from scratch before she's gets too comfortable with this? Flash recommended recovery and reformat sd and reflash everything? (since I originally formatted with Minitool)
BTW it appears that when we install apps will they appear to initially go to internal but after reboot they move to sd, is this actually what is happening and we should always reboot after installs and updates? I just installed about 8 apps and the internal shows it's down to 39mb but then upon reboot it's back up to 76.46 (Originally at 139 but I assume it's all app data consuming it).
Do you recommend anything to occasionally clear app data to ensure there is always space?
For the S3 I would love it if you provided a link to root without tripping the flash counter! Gesh, I love Android more and more everyday (never an issue without solution)... this community rocks!
Click to expand...
Click to collapse
I just tried installing one more app ROM Toolbox (only 8.something MB) and it said insufficent space despite showing the above amount just before install. Before installing or updating anything when I realized the ext was still there, it showed I had 267MB available and I only just installed about 45mb worth of apps, likely updated about 40MB as well. So the ext4 shouldn't be full yet. Could this actually be because of the poor partition?
Ya all that stuff shouldn't be happening. I'm using the same ROM and have non of these issues, so its likely the ext partition.
Your best bet is to start again, and do what I said a couple posts up.
Which S3 variant do u have?
Sent from my HTC Desire using xda app-developers app
Will do thanks. Btw, I'd love the link to the specific rooting method you used for the s3 workout tripping flash counter.
Thanks!
Sent from my SGH-I747M using xda app-developers app
Just missed you asking for my variant. I have the Telus mobility Canadian SGH-I747M.
Sent from my SGH-I747M using xda app-developers app
Gdroid1 said:
Just missed you asking for my variant. I have the Telus mobility Canadian SGH-I747M.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
here you go: http://forum.xda-developers.com/showthread.php?t=1739426
I'm going to attempt this now. First question is that the 4ext instructions say to download the updater, put on sd card and install. Then they instruct you to partition from there. They list the alternative as GParted.
You're saying to use GParted first and then install 4ext to partition. I just want to be sure on this but also if I format first, where I already have apps on sd will this mess anything up not allowing recovery flash or anything?
I suppose once I format the sd based on the current a2sd rom that only recovery will function. Just want to be sure on steps.
Thanks!
chromium96 said:
Well one of your mistakes may have been using mini tool partition wizard. Many users have reported it's unreliability, and i've also had bad experiences with it in the past.
I would recommend using gparted to delete all partitions, and then using it to format the whole card to fat32.
Then install 4ext recovery instead of cwm, and use that create the ext4 partition.
If you need help on installing+using 4ext to create the sd-ext partition check out this guide
Finally do a full wipe, reflash the ROM, and activate a2sd through terminal emulator using:
Code:
su
a2sd install
y
n
y
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Also just to be sure, the link from xda for instructions on gparted say a bootable cd, however usb seems easier, is that okay to use instead?
Thanks (I'm growing
Sent from my SGH-I747M using xda app-developers app
Gdroid1 said:
I'm going to attempt this now. First question is that the 4ext instructions say to download the updater, put on sd card and install. Then they instruct you to partition from there. They list the alternative as GParted.
You're saying to use GParted first and then install 4ext to partition. I just want to be sure on this but also if I format first, where I already have apps on sd will this mess anything up not allowing recovery flash or anything?
I suppose once I format the sd based on the current a2sd rom that only recovery will function. Just want to be sure on steps.
Thanks!
Click to expand...
Click to collapse
i said to use gparted to delete all the partitions, then use 4ext to make the ext partition. But now that i think about it, its probably more efficient to use gparted to do everything. So just follow the gparted method in the guide.
I would recommend creating a 1gb ext4 partition and whatevers left fat32. Also theres no need to make a swap partition for this rom.
Its perfectly fine to format the card even with the apps on it. Again just to recap this is basically what you should do:
1. Use gparted to completely wipe all partitions on the card just for a clean start, then create the fat32 and ext4 partitions (use the guide)
2. Once the partitioning is done, put the rom + and gapps on the card (on the fat32 partition)
3. Put the sd into the phone, boot into recovery and choose wipe data/factory reset, wipe cache partition, then go to advanced and wipe dalvik
4. Flash the rom and gapps
5. Once the rom is flashed reboot and give it a couple minutes to settle. Then run these commands in terminal:
Code:
su
a2sd install
y
n
y
6. From then on, all apps you install should automatically go to the ext partition. I'd also still recommend installing 4ext recovery...i find it better for the desire than cwm.
---------- Post added at 07:48 PM ---------- Previous post was at 07:45 PM ----------
Gdroid1 said:
Also just to be sure, the link from xda for instructions on gparted say a bootable cd, however usb seems easier, is that okay to use instead?
Thanks (I'm growing
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
ya that should be fine. Just make sure you create the bootable usb properly by following the instructions from their site
Why go to the hassel of downloading and using gparted when u can just use 4ext recovery?? if u have a bad partition, 4ext will say ur partitions aint aligned properly or something then u just partition with 4ext recovery. sorted
jmcclue said:
Why go to the hassel of downloading and using gparted when u can just use 4ext recovery?? if u have a bad partition, 4ext will say ur partitions aint aligned properly or something then u just partition with 4ext recovery. sorted
Click to expand...
Click to collapse
he used minitool to partition the card which may have corrupted it. Wouldnt it be safer to start fresh using gparted to wipe all the partitions, so that he wont have any further issues in the future?
chromium96 said:
he used minitool to partition the card which may have corrupted it. Wouldnt it be safer to start fresh using gparted to wipe all the partitions, so that he wont have any further issues in the future?
Click to expand...
Click to collapse
minitool just doesnt align it properly, just use 4ext recovery. so all he has to do is save whatever from the sdcard to pc then partition sdcard with 4ext and it will be done right. trust me, if he flashes 4ext recovery then in recovery, goto tools and check partition alignment and i bet it will say ur partitions are not aligned properly. i tried minitool ages ago to see what all the fuss was about it being sh1te and 4ext said that my partitions aint aligned so i re partitioned with 4ext and all was fine again.
Well this is welcoming because 4ext seems much easier for a n00b like me if it'll work just as well.
I was going to do a 2gb ext4 partition, is that okay versus 1gb?
Btw do you recommend any custom kernel with the desire in this rom? I noticed it is a bit laggy at times and sometimes requires a few taps before certain things activate. Maybe kernels are a little too advanced for me now though?
Or maybe some cpu tweaks or anything. I do own ROM toolbox.
Sent from my SGH-I747M using xda app-developers app
Gdroid1 said:
Well this is welcoming because 4ext seems much easier for a n00b like me if it'll work just as well.
I was going to do a 2gb ext4 partition, is that okay versus 1gb?
Btw do you recommend any custom kernel with the desire in this rom? I noticed it is a bit laggy at times and sometimes requires a few taps before certain things activate. Maybe kernels are a little too advanced for me now though?
Or maybe some cpu tweaks or anything. I do own ROM toolbox.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Anything over 1.5gb for the ext partition is not recommended, so you probably shouldn't do 2gb.
The kernel that comes with the ROM is usually the best for the ROM, and theres not much you can do about the speed in jb roms. Ive tried the supercharger script but i honestly didnt notice any increase in speed. If your looking for a faster ROM use gingerbread.
Also dont mess around too much in rom toolbox if u dont know what your doing, you might get stuck in a boot loop and you will have to reflash the ROM.
All had worked out well and indeed the original minitool said the fat32 wasn't properly aligned. The only thing which keeps aborting is the calendar fix. I noticed chrominum's post about corrupted for our sd, redownload, check md5 and reflash. If doesn't work reformat sd, clear everything repartition and try again.
I did all that and same thing. It doesn't say why it won't work but just aborting per attached.
It did work for me previously in cwm. I only installed the last rc and not the testing version of 4ext.
Sent from my SGH-I747M using xda app-developers app
We were posting at the same time. I'm starting all over again with 1.5g and we'll also see if that helps the calendar fix work.
Thanks!
Sent from my SGH-I747M using xda app-developers app

Categories

Resources