Database Develop

[Q] Questions about the 2.3.3 Hero

I'm running JAChero 2.3.3 and just have a few questions to see if what I'm experiencing is normal.
Firstly, when I'm at the home screen, the trackball cannot select any of the apps, just switch from one screen to the other. Kind of annoying sometimes cause I've gotten used to using it more than the touchscreen. I'm assuming this is a problem on all hero builds, but is there any way it can be fixed?
Secondly, every time I do an adb reboot, the phone boots up then about 5 or 10 seconds later, reboots again. Not that big a deal but just wondering whats happening.
That's really all the problems I have with it, everything else runs great.

Yes the first thing about selecting apps is normal. The second thing, could you be more clear? Do you mean like the htc screen shows again? or does your phone like actually vibrate and go through the 3 screens?

Yes the first thing about selecting apps is normal.
Click to expand...
Click to collapse
Thats depressing
The second thing, could you be more clear? Do you mean like the htc screen shows again? or does your phone like actually vibrate and go through the 3 screens?
Click to expand...
Click to collapse
After rebooting through adb, the phone goes through all the boot loaders, then it starts loading, and while its loading it reboots itself. The once it reboots, everything works fine.

The rebooting is not normal. Dont really have a solution except a fresh format of your ext partition, a data wipe, and then a reflash.

The rebooting is not normal. Dont really have a solution except a fresh format of your ext partition, a data wipe, and then a reflash.
Click to expand...
Click to collapse
I think I'll just live with it, don't really want to go through all the set up again and it isnt really causing any harm.
Thanks for the quick answers alritewhadeva

No problem Cash. Any other questions just PM me

[Q] Nook Color is suddenly really flaky

Long time reader, first time poster (hello everyone!). I was wondering what the opinion of the folks here might be and if they've any suggestions. Today my rooted Nook Color suddenly started acting up. Applications are very often not responding as they should, bringing up the 'Wait' and 'Force Close' box (happens when pressing the soft back and menu buttons as well). It's really quite weird, earlier today I was using it just fine, and suddenly it started acting like this. I tried the usual things like fixing permissions and clearing the dalvik cache, nothing helps. Also, annoyingly restoring a backup from a previous 'known working' state didn't help either. (I suppose I should note that I'm not running CM7 or anything like that)
Any suggestions or ideas on what could have happened? Should I perhaps return it to stock and try to exchange it for a new one (I've only had it for about a month)? The fact that it seemed to still be happening when I restored a back up makes me wonder if it's some kind of hardware issue.
The thing driving me crazy is how it's so suddenly acting strangely. I've been using it rooted (and overclocked, on dalingrin's excellent kernel) just fine for about a month and it's never seemed unstable or anything.

I forgot to mention (not that it probably matters) but the volume buttons caused the wait/force close thing too. Guess I'll be calling them tomorrow.

Having same problems. And VERY SLOW. Wait or Force Close

Very weird, but I noticed today that it started acting flaky in my Nookie Froyo 0.6.8.
I installed Amazon's app store on there today and angry birds rio. The apps seem to be okay, but general opening and navigating are herky jerky.
Something else that is weird, I was just using it and it completely locked up on me to the point of needing to do a hard shutdown by holding down the power. At the exact same time, I happened to look at my phone and it also had rendomly rebooted itself at the exact same time. My phone is running CM7 (Droid1).
Coincidence?

HI,
I had a variety of problems with similar symptoms as you describe, but I had
been playing with several uSD installs of HC/Froyo/CM7 internal/Froyo internal etc.
I believe that the main cause of my problem was due to an interaction between
the EXT3 and EXT4 formatting of the cache partition. The solution for me was to
reformat the cache partition for my current installation.
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Not sure if any of these are relevant to you though.
Good luck.
Peter

Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!

pmilford said:
HI,
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Click to expand...
Click to collapse
Thanks, but I tried those already (I forgot to mention it in the first post, but I did try reformatting the cache partition).
JLCollier2005 said:
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
Click to expand...
Click to collapse
Yeah, I guess that's a good idea. Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.

9thSage said:
Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
Click to expand...
Click to collapse
All I'd need to do to install Froyo from here is format/factory reset everything with clockwork and then install the zip from within CWM, correct?
Couldn't get it to work for some reason. Since I wasn't sure, I decided to format data, cache, and system, then use one of the excellent "Nook Color Restore to Stock" zips. It seemed like it was ok (couldn't test it more since I forget my B&N password and evidently made a typo when tying my mother's maiden name ), decided to try that back up again since I knew the back up worked at one time with no problem (and the md5 was fine, so that shouldn't have changed) and it worked fine for maybe 20 minutes, but now it's weird again.
I'll have to try Froyo again tommorow when I'm hopefully less out of it. I suppose that's probably a more meaningful test.

I know I said I was going to install Froyo, but I decided to try bringing it back to stock and re-rooting it from scratch. I've been using it for a while (reinstalling apps, changing settings back...etc) and it's worked absolutely fine. Been using it on and off for a few hours.
I'll be sure to really bang on it today to make sure it's stable, but so far so good.

I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.

9thSage said:
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
Click to expand...
Click to collapse
Glad to hear! I actually just had a similar problem (again on my Droid) that it ended up being the ROM, but yet everyone else I know had no problem on that rom....just goes to show you Android is different for every unit.

[Q] Lock Screen Password Enabled Even After Factory Reset

hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!

h2whoa said:
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.

ArtfulDodger said:
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
Click to expand...
Click to collapse
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.

h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app

h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
Hate to hear that and you're not the only one to mention swollen batteries around here lately either. Good luck to you!

theAPANT said:
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?

h2whoa said:
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
Click to expand...
Click to collapse
Yes the easiest way to get rid of cwm is to flash the stock file. Go to http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G there are, i believe two methods, one using Odin the other flashing something in recovery. Just read. As for cm10.1 camcory is working on it so is smartguy. Even i compiled it but it doesn't boot all the way. Check insomniaforums.org that is probably where it will be posted
Sent from my Nexus 7 using xda app-developers app

CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium

afwolfpacked said:
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Bluetooth and camera dont work. I'm saying my own personal build doesn't boot yet but I'm trying some stuff. Right now I'm working on aokp 4.1.2 to get that fixed all the way, mainly because i like aokp and I'm stuck on 4.2.2
Sent from my Nexus 7 using xda app-developers app

[Q] Stubborn Sleep Of Death... Help please!

So recently my touchpad turned off and not turn back on. I thought it was toast the first time this happened. Turns out, I just needed to hold the power button and home button at the same time for like 20 seconds and it came back to life. I'm pretty sure in this instance I had let the battery drain pretty far, yada yada yada.
Anyway, I got it charged back to 100% and everything seemed ok. But it would have random reboots a few times an hour. Also, when I turned the screen off, even at 100% battery, about 10% of the time, the thing would not turn back on unless I held down the power button and home button and rebooted the thing, a la sleep of death.
Per some advice I got from these forums, I redownloaded the ROM, tried different ROMs, Wiped everything multiple times before flashing, removed Android completely with ACME and wiped WebOS completely back to factory and wiped WebOS USB.I reinstalled Android and no matter what ROM I am on, I still get sleep of death just about every time I use it.
I have also tried bumping the minimum CPU speed and even installed a cool app call softlocker that seemed to help a little bit, bit this thing just keeps wigging out.
So, my question is, does anyone know what the hell I am doing wrong? Has anybody come across this before? Every search I do on this is just to get it back to life when you let the battery drain. This is happening to me at 100% battery.
I am about to sell the thing and chalk it up to hardware going bad unless anyone can help. I guess I could probably get some logs with logcat but I have never done it before and don't really know how to read them.
HELP FROM A FELLOW ANDROID TOUCHPADDER>

I have seen /helped with a similar problem, he was in exactly the same situation as you. What fixed for him was to acmeuninstaller android then webos doctor 3.00 followed 3.0.5 and finally reinstalling android.
Sent from my cm_tenderloin using Tapatalk 2

Thank you sir. Is 3.0 and 3.0.5 the webos doctor version or the webos version? I heard if you update webos to the latest ota, you can't install android anymore.... will look into this. thanks.

Flandro said:
Thank you sir. Is 3.0 and 3.0.5 the webos doctor version or the webos version? I heard if you update webos to the latest ota, you can't install android anymore.... will look into this. thanks.
Click to expand...
Click to collapse
It's webos doctor use that to give you 3.0.5 rather than ota it's safer anyway and yes you can put whatever you want on it.
Have fun.

sstar said:
I have seen /helped with a similar problem, he was in exactly the same situation as you. What fixed for him was to acmeuninstaller android then webos doctor 3.00 followed 3.0.5 and finally reinstalling android.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I just did all this and booting back up into android now. Will report back after some use.

Seemed to have done the trick. Thank you so much!
Sent from my cm_tenderloin using XDA Premium HD app

Flandro said:
Seemed to have done the trick. Thank you so much!
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Your are more than welcome I am so glad it has worked for you also. All the best.

[Q] Odd shutoff issue...what to do?

Every so often my Kindle Fire 7 hd will shut off. Not reboot. It will completely turn itself off. It is very random. Sometimes it works for a while and the boom it happens. Doesn't seem to matter what I'm doing at the time. Sometimes it is when I unlock the screen...sometimes when the screen rotates...other times when I'm opening an app, or using an app.
There were times that after it would shut off I would turn it back on and it would almost be finished started up, but then turn itself off. I would have to plug it in in order for it to completely boot up.
One thing I've noticed is I don't seem to have any issues when the unit is plugged in. Could be just a coincidence though. The battery is 50%+ when this happens.
It started this about a week ago or so. At that point I had used KFFirstAide to put 7.2.3 on and was running Nova as my launcher. I thought it might be a ROM issue so I installed TWRP and put Kinology on it. Well, it is still happening.
So, it seems like I might have to make a call to Amazon (although I bought it Oct. 2012, so I doubt it is under warranty). I assume I will need to get the whole thing back to stock...unless someone here has a different suggestion).
Thanks for any insights/help you might be able to provide!
Dave.

I have a similar issue where my Kindle now wants to shut down as I open the case????? This is a new problem and I've also noticed that the battery life is getting worse. Anyone else having these problems and got any ideas on how to fix?
Steve
Sent from my KFHD7 using xda app-developers app

@galearned is dealing with a similar issue regarding a KFHD7. I think the three of you should get together to try and find a common denominator.

Slangster said:
I have a similar issue where my Kindle now wants to shut down as I open the case????? This is a new problem and I've also noticed that the battery life is getting worse. Anyone else having these problems and got any ideas on how to fix?
Steve
Sent from my KFHD7 using xda app-developers app
Click to expand...
Click to collapse
Galearned here: I am running CM10.1 on my KFHD7 and do not have any shut down issues as far as I know but, regarding battery life, the unit is pretty bad compared to the KFHD8 also running cm10.1.
I traveled to Cleveland this last weekend and took my KFHD8 with me.
I used the KFHD8 the entire trip on the plane (several hours of fooling around and shopping on Ebay (free ebay on the plane).
I also used the KFHD8 both Saturday and Sunday extensively and Sunday evening, I checked the battery and it was down to 20%.
Until then, I did not plug in to any power supply.
I know for sure the KFHD7 would never had gotten that far.
One thing I have not checked is how quickly the battery drains on both units while doing the same tasks.
Most of the comparisons including the one I posted, indicate that while asleep, the KFHD continues to drain loosing several points over night.
If you leave the KFHD7 asleep for several days, the battery will be down to the 20% level or lower.
The KFHD8 will not loose more than a single point after several days setting asleep.
_________________________________
Update : CM 10.1 Deepsleep release 07/26/2013
Loaded this 07/26/2013 version last night on KFHD7 and configured wifi to be off while asleep as usual.
Tablet was fully charged at 11M and at 7AM still showed battery at %100%.
Very Very nice. Looks like Hashcode came through again............

So, you're saying the shutdown issue ceased after installing CM?

I have the same problem, running CM 10.1
I just flashed CM 10.1 a few days ago and just started to have these random shut offs... usually when the battery is around 60%. I thought it was the ROM, but seeing you guys have the same problem, I´m thinking there is something else involved. I never had those shut offs on stock.

Well, exactly same problem with no apparent solution. I think the problem started when upgraded to 7.3.1. After that I disabled OTA, tried to uninstall all applications added by me, disabled all notifications, etc.. but the problem is not solved

Elgari said:
Well, exactly same problem with no apparent solution. I think the problem started when upgraded to 7.3.1. After that I disabled OTA, tried to uninstall all applications added by me, disabled all notifications, etc.. but the problem is not solved
Click to expand...
Click to collapse
Are you on Stock OS? If so, have you changed the Kindle's DPI? When I was on stock, I changed my DPI to 213 (same as Nexus 7) and started having random rebooting issues. Changing the DPI back to default (240) fixed the problem.
Just my two cents

Ph0enix_216;47286524 you on Stock OS? If so said:
Thank you for your post. I m on stock OS, but I dont know how to change DPI!!
Click to expand...
Click to collapse

Elgari said:
Thank you for your post. I m on stock OS, but I dont know how to change DPI!!
Click to expand...
Click to collapse
If you don't know, then I'm guessing that you never changed it, which means that it's probably not the problem. However, if you want to check, download ES File explorer from the Play Store, and navigate to "/system." There should be a file there called "build.prop." Open it, and look for this line (the value should be set at 240).
Code:
ro.sf.lcd_density=240

Ph0enix_216 said:
If you don't know, then I'm guessing that you never changed it, which means that it's probably not the problem. However, if you want to check, download ES File explorer from the Play Store, and navigate to "/system." There should be a file there called "build.prop." Open it, and look for this line (the value should be set at 240).
Code:
ro.sf.lcd_density=240
Click to expand...
Click to collapse
Thank you! I did what you said but, exactly as you anticipated, it was properly configured.
But the problem persists and I can not find any solution anywhere!

Elgari said:
Thank you! I did what you said but, exactly as you anticipated, it was properly configured.
But the problem persists and I can not find any solution anywhere!
Click to expand...
Click to collapse
You could reflash the entire system image. Download Kindle Fire First Aide (it's in the "General" section of this subforum) and follow the steps there. Once it's set up, select the option 3 (assuming that you have a KFHD), which will let you choose to restore to either the 7.2.3 or 7.2.1 OS. It says "fastboot," but I don't think you need a fastboot cable for it.
OR, if you have TWRP enabled, you can go here and download Amazon OS 7.4.6, but comes pre-rooted and has OTA updates disabled. Put this on your SD card, reboot into recovery, and wipe your current ROM and install this.

Ph0enix_216 said:
You could reflash the entire system image. Download Kindle Fire First Aide (it's in the "General" section of this subforum) and follow the steps there. Once it's set up, select the option 3 (assuming that you have a KFHD), which will let you choose to restore to either the 7.2.3 or 7.2.1 OS. It says "fastboot," but I don't think you need a fastboot cable for it.
OR, if you have TWRP enabled, you can go here and download Amazon OS 7.4.6, but comes pre-rooted and has OTA updates disabled. Put this on your SD card, reboot into recovery, and wipe your current ROM and install this.
Click to expand...
Click to collapse
I already did the first option you mention, but did not solve the problem.
I will try with the second option. I do not know if I am able to make it!!
And yes, I have KFHD (and I make a factory cable).
Thanks again!

Elgari said:
I already did the first option you mention, but did not solve the problem.
I will try with the second option. I do not know if I am able to make it!!
And yes, I have KFHD (and I make a factory cable).
Thanks again!
Click to expand...
Click to collapse
If you tried the first option, and you're still experiencing the problem, then it might be something you're doing, such as installing a specific app or mod or something.

Ph0enix_216 said:
If you tried the first option, and you're still experiencing the problem, then it might be something you're doing, such as installing a specific app or mod or something.
Click to expand...
Click to collapse
Yes, I think that too! In last month I uninstall all my apps one by one but I do not find the problem either!!
Did you think to have OTA disabled can cause the problem?
I hope tomorrow read To learn about TWRP and try with that.

Elgari said:
Yes, I think that too! In last month I uninstall all my apps one by one but I do not find the problem either!!
Did you think to have OTA disabled can cause the problem?
I hope tomorrow read To learn about TWRP and try with that.
Click to expand...
Click to collapse
OTA shouldn't be the cause. Lots of people have had OTA disabled without any problems. Honestly, I have no clue what the problem is

Ph0enix_216 said:
OTA shouldn't be the cause. Lots of people have had OTA disabled without any problems. Honestly, I have no clue what the problem is
Click to expand...
Click to collapse
Well, the problem the problem has worsened which led me to decide install TWRP.
I read about TWRP and second bootloader and try three times with Hashcode´s method but I cant do it. I´m very frustrated for my inability!!!
Thanks anyway for your help.

Have any of you tried calibrating your battery?
Sent from my JellyBeer Fire HD

Krsmqn said:
Have any of you tried calibrating your battery?
Sent from my JellyBeer Fire HD
Click to expand...
Click to collapse
I tried to install TWRP but after three attempts I could not do it and bricked my KF. So I install everything new with KFFA. The bad news is that the problem continued. I'm starting to believe it's a battery problem and not a problem of the apps. Yesterday its worked all day (with tunein radio) without problem and just spent 20% of battery. But today when I wanted to put to work again made the same problem.
How can I calibrating the battery as you suggest? I think the problem is for this side.