Database Info

[Q] Problems with most Roms

I am unlocked and have the recovery of twrp 2.3.3.0. I'm having problems with about every single rom I flash. I wipe everything as you are suppose to and the flash appears to go well but usually right away after the rom boots up the system becomes unresponsive. I have to hold my finger over a button for a couple seconds for it to acknowledge a touch and things just don"t run right.
Its like either the system is almost locked up or the touchscreen just hardly works.... one of the two. I made a backup of my original asus setup and if I restore it the tablet works just fine. I've tried hydro, cm 10.1, blackbean 7, and one or two I'm forgetting. AOKP RC1 is the only custom rom that gives me no problems at all in this regard, unfortunately its an unfinished rom, no camera and my battery dies like crazy with it...
The 2nd best running rom that I really like from what I have seen is blackbean 7. Runs great for first few minutes but after playing a game for a bit or doing some other things and having it run just great all the sudden the dreaded problem occurs and the only fix is a reboot for it to work for a while longer. So frustrated at this point as I have flashed so many roms and resetup so many things just to find myself doing it again trying to fix this and find a rom that works for me.
Any ideas at all on what could do this? Is the difference in the kernels the reason why AOKP RC1 and Asus original work but none of the others? Or does it have to do with my recovery? Fairly certain I have the correct most recommended one with twrp 2.3.3.0 and the process went fine. Any ideas greatly appreciated. I really just want to be able to run blackbean. And knowing that most all roms will not work for me is rather disturbing in regards to the future. Really wanting to like my new tf300t but its making it hard:silly:

Try to downgrade your recovery.
Use this : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
and take a feedback after, thanks

I really appreciate that you took the time to give me something to try but I'm afraid it didn't work. Process went fine I'm on 2.3.1.0 twrp but same problem. First rom I've tried instant non-responsive. Any other ideas?

I've been using ClockWorkMod Recovery on my TF300T, and it's been great. (Used it to upgrade my ROM to CM 10.1.) No issues at all.
If you need instructions for getting it installed on a TF300T, check out my second-to-last post on thoughtsontechnology.com. (NONE of the work is mine, I just compiled the instructions and links in one spot for easier access. Most of the work came from XDA contributors, they've been really great.)

Most roms need 5 to 10 mins to stabilize after a new install, usually as they are building media storage files, etc. Are you giving them enough time?
Failing that I can only think your microsd has something corrupt on it. Boot with it out.

Well I tried cwm again flashed it no problem installed rom no problem but no fix. So guess we have established it definitely isn't the recovery at this point...
Yes I've given roms several reboots and lots of suffering them working for 10min to only fail again for another reboot... So its not that. Still the only Rom that will work is my backup of the original asus and the AOKP RC1. Trying it without the external sdcard right now.
Well no joy on the removal of the external sdcard

Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I

sbdags said:
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
Click to expand...
Click to collapse
Not sure what a full wipe is? I wipe cache/dalvik system format data and have even tried formatting the sdcard once several roms ago. One thing I have noticed since I am trying so many roms all the time is the sdcard file structure seems odd as I have at the root of the sdcard a 0 directory that continues to be added to. Currently it goes sdcard/0/0/0/0 to actually get to where I have things stored like music, downloads. Is this normal? Its strangely repetitive.

Personally I think you should stop using TWRP if you're having all these issues. Just flash CWM and have fun

touchscreen
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?

Showme1 said:
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Click to expand...
Click to collapse
Sounds like you have a hardware fault if the issue persists across multiple firmwares.

Also, OP said his SD card directory structure was strange. I'd format both internal and external SD in recovery (in addition to wiping and factory reset) before you flash.

Thanks! Wiping internal has seemed to do the job. Still would like to know what the issue was. I was thinking it was the touch panel firmware, but thought that would be in /system
Sent from my SGH-I747 using xda app-developers app

Re: [BeanStalk][1.179] Phone freezes after call

Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over

qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.

bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.

qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.

bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo

OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548

[Q] Voicemail notification issue on crespo4g w/ AOKP/4.2.2

Hi all - This is my first post and I am sorry if I'm breaking a rule. I have tried searching for a resolution to this issue before joining up but could not find anything specific to my phone, rom, issue.
Background:
I rooted my phone a while back but for some reason never flashed to a custom rom, just wanted the root. Last week I flashed after some trial/error to AOKP. I cleared the data/cache and did a fresh install of AOKP 4.2.2 with the 2013-03 package of GAPPS. I installed my Titanium Backup'd apps overtop via the app, not an update.zip.
Situation:
My voicemail notification is not going away after I get a voicemail. I will get the notification (sometimes quicker than other times) but after I call my voicemail, listen to the message and delete it the notification does not go away. I have to go into the Phone app-info and force stop/clear data for the notification to go away.
Phone details:
Sprint Samsung Nexus S 4G
AOKP 4.2.2 (goo.im-devs-qnhoang81-crespo4g - aokp_crespo4g_unofficial_2013-05-25.zip)
GApps gapps-jb-20130301-signed.zip
No custom voicemail program - typical Sprint voicemail setup.
If no one is aware of a good resolution with my specific setup, I would also appreciate suggestions of ROMs w/ latest Android that fellow Sprint customers arent having this issue with on the Nexus S 4G.
Thank you very much and I appreciate your patience if I did something wrong with this thread.

I've had this happen with slimrom. I either did a funky flash or found some other way of mucking up my install.
I eventually just did a full wipe and have been fine ever since.

weedy2887 said:
I've had this happen with slimrom. I either did a funky flash or found some other way of mucking up my install.
I eventually just did a full wipe and have been fine ever since.
Click to expand...
Click to collapse
+1 to doing a full wipe (then adding) re-install...
If a full wipe and re-install doesn't fix your issue with the rom ( as I can't speak for app behavior ) flash back to stock and start over, remembering to always back up your data first..

Thanks guys, thinking back I went from stock 4.1.1 to AOKP 4.2.1 then to AOKP 4.2.2. I thought I did clean installs both times. Is it possible that something with my Backup apps is causing the issue? Like if I'm restoring phone settings from a previous version to the new version?

If that didn't fix it.... go into settings/ Apps scroll along the top until you see ALL apps and scroll down to phone...clear data...

[Q] P5110: Random Rebooting (CyanogenMod 10.1 - RC5)

My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!

jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,

jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
Have you done any undervolting or anything? That can cause this.
If not you may try doing a full wipe and reinstall of the ROM. Clearly you've got something borked up that an update flash isn't fixing. A full wipe may solve your problem. It's a pain in the rump, but sometimes you have to do that.

Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
Ive been having this same problem for the past few days now also.
I tried reinstalling rom with these exact instructions and after installing some of the basic apps i use, the tablet restarted itself again.

Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium

Siddharth121 said:
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
any suggestion on which kernal to try?

Domino_13 said:
any suggestion on which kernal to try?
Click to expand...
Click to collapse
Never mind my post. I got my devices mixed up.
Sent from your phone. You should be careful where you leave that thing.

Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium

Siddharth121 said:
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
It started for me when I upgraded from CM10.1 M3 to CM10.1RC3 i think it was. I have tried upgrading to Rc4 and RC5 also but same problem with the rebooting.
I also tried to go back to M3 but it was also just rebooting randomly.
Before I upgraded to RC3, I never had a problem with the tablet.

Problem Fixed...Hopefully
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.

Normal practice for rom flashing
It is in my, and many others experiences that a failsafe way to flash a ROM is as described below..
Note: this is assuming that you have already downloaded the rom you want and placed it on your sdcard/external-sdcard and that you have a custom recovery like clockworkmod or twrp...
Reboot into recovery
Make a backup of your current system
Tip: its always better to have a removable external_sdcard when doing any kind of root tasks but not needed
Now for the ROM..
1. go to mounts & storage and select it
2. Scroll down to the "format" section
3. Now select format system (and then yes)
4. Select format cache (and then yes)
5. Select format preload (and the yes)
6. Select format data (you get it)
If you don't have an external_sdcard don't format anything else and proceed to step 8
Now if you have a (removable) external_sdcard and you have placed the ROM and gapps on it, then you should;
7. Select format sdcard (the NOT REMOVABLE, internal sdcard space)
8. ***go back***
9. Install zip from sdcard/external_sdcard and proceed with your normal install procedure...
By doing the format methods before installing a new ROM, you're insuring that the ROM is writing to all freshly wiped partitions on your device and this will always be the most redundant way of making sure something did not get left over from your previous setup.
Most install.zips that the ROM is packed up in do perform the format of system, data, and cache during the install and usually it works fine but however, it is not always reliable.. By doing the few extra steps above, you will always know that the installation is a clean one and will greatly reduce problems like described above in this thread.. Why not just be sure?
---------- Post added at 07:24 PM ---------- Previous post was at 07:00 PM ----------
If you have done a "FULL WIPE" like I described in the post above and your device is still randomly rebooting..
Then it is most likely due to something having to do with the kernel.
There are many reasons why it could be triggering the "panic" feature in android but the most common ones are;
Over clocking.. Either your devices processor CPU OR GPU, cannot handle being scaled up to the frequency that the ROM sets it at, or
Unstable... The kernel that came with the ROM you are installing is not yet stable enough for daily use and is in need of more debugging/development.

jqcaffeine said:
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Click to expand...
Click to collapse
You had either an app or a setting that wasn't doing what it was supposed to. That is the only way a factory reset would fix it.
That also means the problem could have been fixed without the reset. You would have just had to isolate the error, which obviously is tough. Just keep that in mind if it happens again, immediately try to remember the last thing you changed, the last app that was updated, the last setting you altered, etc. Then maybe you can fix it faster without the hassle of the reset.
Glad its fixed!
Sent from my HTC Sensation using xda app-developers app

After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.

Domino_13 said:
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Click to expand...
Click to collapse
Which kernel?
I'm very new to this kernel stuff, I got the hang of roms (I think) and I'm now using Cyanogenmod. I read somewhere it already includes it's own kernel, correct?

All roms come with a kernel as part of the install package. You can change to different kernels as well.
Right now for the t mobile phone i think there is just the stock cm kernel and albinoman887's kernel. The aokp roms probably have some other kernel tweaks in their stock kernels
Sent from my SGH-M919 using xda app-developers app

Don't forget DhollmenCM Kernel.
Posted from my Galaxy Tab 2 with CM10.1

I am Having the same prob with galaxy tab2 7.0(gt-p3100)

[Q] XT926 Stuck on 11/07 CM 11

I have an XT926 running KKBL CM11 nightlies and have been updating through Cyandelta since Towelroot gave me an unlocked bootloader (thanks Geo). I have been updating without issue until the 11/07 nightly. Ever since then, Cyandelta shows no updates but if I go through the CM Updater, it shows all of the updates released for the moto_msm8960. If I try to apply any of these updates outside of Cyandelta (either through CM Updater or flashing full zip through recovery), I can boot my phone but will start getting a persistent error saying "There's a problem with com.android.phone process and it has to close" or something to that effect. I have tried wiping both caches and even doing factory resets but the process crashing starts back within a few minutes of getting everything set up. I did notice that even though I did a factory reset, all of the apps I have installed still had data from before the wipe so I feel like the wipe is missing something that is causing the crash(?). I've been using custom ROMs for a while on a few different devices but this is the first time I've ran across this. Any advice?

Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.

CWGSM3VO said:
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
Click to expand...
Click to collapse
I've never had to go further than a factory reset before. Which partitions should I format?

I'd format system, data, cache and dalvik. Definitely time to flash clean.
When I had my XT926, I also found that after so many updates via Cyandelta, that I would get the same issue. I would then go back, clean flash the latest update and things would be good. I eventually stopped using Cyandelta altogether. It's a nice idea, but I just don't know if I completely trust its abilities in determining what to bring down and what not to. I'd rather go with the CM updater instead. Yeah, it means longer downloads, but which is longer: downloading the full update from CM and having it work, or downloading via Cyandelta and then having to wipe clean, install and then restore all your backups?

iBolski said:
When I had my XT926,
Click to expand...
Click to collapse
You did abandon ship!

lloydsw said:
You did abandon ship!
Click to expand...
Click to collapse
Yup, but I stated in my post (where I said my goodbyes), that I would still hang around and help out. I know there are a lot of people still on this phone, especially with CM12 now running on it.
But, loving my G3. Still on stock, though (4.4.2), but I have no reason to go to anything else right now. Runs smooth, but it is rooted so I can run TiBu and also enable SD writing. But, I have no other reason to go to CM12 at this time.
I can get at LEAST one day if not more. Usually, after 24 hours, I'm right around 50% on battery. I probably could go even longer, but definitely I get more battery life out this phone than I did on the XT926 (non-MAXX), but I was able to do the same on my non-MAXX, but only if I didn't use it much. With the G3, I can do quite a lot and make it through the day without having to recharge during the day. I love that!
In any case, I'm still lurking about these forums to see if anyone needs help.