Related
I've never participated in a forum where experienced members refused to assist others. Even other xda forums seem more helpful than this Athena forum.
I bought an x7501 off ebay a few days ago, and I've been playing with it. It's performance is not consistent, and I'm wondering if it is defective.
It was sold as NIB (new in box) and it appeared to be unopened when I received it, but I can't be 100% certain that is the case.
Some simple operations are grossly slow. The problems are intermittent, the worse kind to trouble shoot. Recently, I tapped on the CommManager icon on the Today screen at it took 15 seconds to open CommManager.
When I first received the unit, I installed Google Maps and tried out the GPS. I was able to connect to GPS inside my house. This morning I couldn't connect in my car, and when I stopped the car, I tried to connect standing outside in the open. After about five minutes, it wouldn't connect, so I went inside my house, and after a few more minutes, it did connect. While I was waiting for it to connect, I got my Kaiser and opened Google Maps and connected to GPS withing a few seconds outside in the open.
I had installed Opera 9.5 beta and NetFront 3.5 as well as RealVGA and MvRTrueVGA, and after running into strange display artifacts and bugs in the beta browsers, I decided to clear everything out, and ran the Clear Storage utility in System Settings. I had done this once before when trouble shooting failed attempts to connect the Athena to my Belkin Pre-N WiFi router.
So, now, all that's installed other than the what came on the phone is Google Maps and NetFront 3.5.
The battery performance is also a bit strange to me. It seems to be discharging even when I have it connected to my computer using the USB cable. Nothing is open in the background, and I wasn't using it, but it showed 70% when I connected it, and thirty minutes later it showed 60%. Is that normal?
Is the ROM that shipped with the phone questionable?
Might I get better, more reliable, more consistent performance with one of the ROMs available here?
I'm not ready to give up, but I'm not encouraged at the moment, and I'm not sure what to do next.
May I suggest Dual PK 3.0. Try backing up all that you have now and flash it with Dual PK and let us know the update.
Regarding the battery drain issue, most computer USB ports and non-factory chargers don't give enough power to even maintain (let alone charge) if you have all the radios on. Especially the GPS radio which seems to need a lot of power - I can go all day with the cell and bluetooth radios on and still have 90% charge after 16 hours, with little cell or internet use. But if I turn on the GPS it will be discharged within a few hours.
Computer USB ports are usually limited to 500 milliamps, and some chargers are less, so the only good solution is to only use the factory charger if you have everything on. Turn down your screen brightness, too. I leave mine at 50% both on the battery and when plugged in, except in full sunlight.
As for the GPS reception, its very bad. I have a sirf/star mouse-style GPS unit which locks on within seconds in the middle of the 1st floor of my 2-story house, attached to my Palm or a computer. My X7501 usually won't lock on even when I'm near a window. I rarely have a problem outside or in my car, though. I'm one of many that have reported similar issues.
I usually don't see slowdown issues, but I sometimes do if the wifi or GPS radios are on. Try only running cell and bluetooth for a while and see if that helps. I also found that Opera would slow down more, and then more, and even more as the cache filled up, but that was after I changed it from the default "1000". I cleared my cache and changed it back to the default cache size and I've been fine since.
Hey TnT,
Thanks for the detailed feedback. I'm going to play with it some more. I'm planning on flashing a different ROM, as TT2 suggested.
Which ROM are you running?
Try PK dual black... but don't for get to Hard SPL...
Please don't install anythink on your Harddisk, just install on storage card... My athena run fastrer if i put seftware on SDcard... If install ti HD it will slower.. i've tried it
thanks cornelius, i'm in the process of gathering the info and parts to install a new ROM. I've downloaded the "AP Dual 3.0 ROM" - I think that's the same thing as the PK Dual Black. I've also downloaded the AthenaUnlocker.exe - I think that's the hard spl you mention.
I bought my phone unlocked - I gather that's SIM unlocked, and the AthenaUnlocker will CID unlock it, which is necessary before installing the new ROM.
I'm trying to confirm everything, so I don't brick the phone, but I'm the information is scattered all over the forum and wiki. I found two versions of AthenaUnlocker.exe, both version 1.0.0.0 with different time stamps. I tried to watch a video of unlocking, but there was no audio.
I would appreciate any additional pointers in the process.
Thanks
Im running the factory ROM.
xdafile said:
thanks cornelius, i'm in the process of gathering the info and parts to install a new ROM. I've downloaded the "AP Dual 3.0 ROM" - I think that's the same thing as the PK Dual Black. I've also downloaded the AthenaUnlocker.exe - I think that's the hard spl you mention.
I bought my phone unlocked - I gather that's SIM unlocked, and the AthenaUnlocker will CID unlock it, which is necessary before installing the new ROM.
I'm trying to confirm everything, so I don't brick the phone, but I'm the information is scattered all over the forum and wiki. I found two versions of AthenaUnlocker.exe, both version 1.0.0.0 with different time stamps. I tried to watch a video of unlocking, but there was no audio.
I would appreciate any additional pointers in the process.
Thanks
Click to expand...
Click to collapse
Just make sure you've got a fully charged battery before attempting to unlock or flash the ROM. If you have any particular question feel free to jump back in and post it. Oh and btw The PK Dual is what I was talking about in my last post...Sorry if it seemed a bit confusing.
I'm getting a error when I attempt to unlock my phone.
I ran version 3.12.3.3 of AthenaUnlocker.exe. The error is 202 connection.
the update utility cannot connect to your pda phone. please check that your usb cradle/cable is connected properly between the pc and your pda phone.
check the following:
1. the pda phone is connected to the usb cradle/cable.
2. the usb cradle/cable is connected to the pc.
I know the phone is connected. It is synchronized with ActiveSync 4.5, and it shows that it is connected.
Maybe I don't have the correct version of AthenaUpdater?
I've made progress with the AthenaUpdater.exe program.
I noticed that I had to take an action on the phone after I started the update process. I didn't notice that before, and there is nothing in the program that tells the user to check the phone.
Anyway, step one completed, and I completed step two.
Now, the phone won't turn on. I remember reading about a special key combination, and I'm wondering if I need to do that to get it to turn on and complete step three.
If I get through this successfull, I am going to update the wiki with a how-to for the next guy new to the Athena.
I found the key combination to get into the bootloader,
camera - power - reset
I continued with setp three of the AthenaUpdater, but I think because of the errors, the update did not work properly.
The phone will still not turn on.
I can get it to go into the bootloader, but I don't know what to do next.
I would really apreciate if someone who know what to do would post some helpful comments now.
Thanks
when I go into bootloader it displays
ATHE100
IPL-V2.02
ATHE100
SPL-v1.20.Olipro
At this point, can I install the AP Dual 3.0 ROM?
I installed AP Dual 3.0 with no problem.
However, GPS seems to be not working.
Do I need to run the AthenaUnlocker.exe again?
Does that mean I'll have to reinstall the AP Dual 3.0 ROM again?
Wish I could help you, but I've never updated my ROM. Maybe the version coming on the X7510 will entice me to try.
What error are you getting when you try to run Google Maps? If you get an immediate error, your ports aren't set right. If it spins its wheels for a while the ports are right but the fickle GPS is taking its time.
Tonight I'm going to try and straighten things out on my Athena.
I hope I don't have to spend hours at it again. It would be great if someone who know has experience with the unlocker and the AP Dual 3.0 ROM could spend a few minutes answer my questions so I won't have to spend a few hours sweating through the upgrade process. Last night I literally was as sweaty as if I had gone for a jog; I was surprised at how stressful the upgrade process was for me (I mean, it's only a few hundred dollars if I brick it, right?)
The state of my Athena now is: I probably botched the unlock process in step two, because my GPS is no longer working.
Can I just run the AthenaUnlocker again, or do I need to first flash back to the original x7510 HTC ROM?
After I run the unlocker again, do I need to flash the AP Dual 3.0 ROM again?
I'm also wondering why I ran into problems with the unlocker, and concerned that I'll just encounter the same problems again. I'm hoping that because I have the AP Dual 3.0 ROM installed, the unlocker will perform differently and without errors.
If anyone is reading this who knows the anwser to my questions, I'd really appreciate hearing from you.
Thanks
techntrek said:
What error are you getting when you try to run Google Maps? If you get an immediate error, your ports aren't set right. If it spins its wheels for a while the ports are right but the fickle GPS is taking its time.
Click to expand...
Click to collapse
Error message???
TechNTrek,
Thanks again for pitching in to offer me help.
Good new for me; The GPS started working. Earlier this morning, I decided to try it again outside, giveing it more time, and it connected. It had been bringing up a message screen telling me about connection problems.
I just tried to bring up the can't connect message screen by attempting to connect while inside my house, but the darn thing connected with 7 active satellites, and I can't reproduce the problem now to give you a detailed error description.
So, even thought I got a bunch of error messages during my unlocking process, the unlocking seems to have worked, and it left my Athena in working condition.
Some final notes relating to how I started this thread: now that I have AP Dual 3.0 ROM installed, the device seems to be performing better in all the problem areas I first mentioned.
I tested charging the battery by connecting to my computer's USB port, and, although it is charging slowly, at least it's not discharging while connected.
I think that experience discharging while connected might have been because Opera 9.33 beta was open to a page the was running something - just speculation.
I think it's also possible that I misinterpreted what I saw; it might not have been discharging while connected; instead, it might have been a delay in updating the display of the state of the battery; when I looked at the battery when I first connected to the USB, it showed 70%, but in reality it might have only been 60% charged, and the display had just not updated; then, when I disconnected it, the display had updated to the correct 60%.
Also, I haven't noticed any of the extremely slow performance when open apps or running apps. I did notice that my old Kaiser is a lot snappier than the Athena before I updated the ROM. I'm going to keep an eye on it, and do some more Kaiser/Athena performance comparisons.
I think the Athena may be slower than the Kaiser because of the video driver issue. The Athena has four times as many pixels to render, and the CPU has to do the rendering since the driver that would take advantage of the ATI video processor is absent. Hopefully, that will be fixed soon, as mentioned at HTCClassAction.org. http://www.htcclassaction.org/
I am going to start a new thread on a couple of questions I have. In the original HTC ROM, there was a network program from HTC, and I used it to connect to shares on my LAN over WiFi, and I want to find a replacement for it. There may even be a network program in the Dual 3.0 ROM, but I haven't found it yet.
Also, I love MS Voice Command 1.6 (a version made available in the Kaiser forum - not a more recent 1.6 version for sale by MS.) It works for me on my Wizard and on my Kaiser, but on my Athena, I can't start Voice Command using my Bluetooth headset.
I've searched both of these issues in the forums, but haven't found answers yet. Again, if anyone knows, please help.
Now, I'm going to explore the 3.0 ROM!
xdafile said:
TechNTrek,
Thanks again for pitching in to offer me help.
Good new for me; The GPS started working. Earlier this morning, I decided to try it again outside, giveing it more time, and it connected. It had been bringing up a message screen telling me about connection problems.
I just tried to bring up the can't connect message screen by attempting to connect while inside my house, but the darn thing connected with 7 active satellites, and I can't reproduce the problem now to give you a detailed error description.
So, even thought I got a bunch of error messages during my unlocking process, the unlocking seems to have worked, and it left my Athena in working condition.
Some final notes relating to how I started this thread: now that I have AP Dual 3.0 ROM installed, the device seems to be performing better in all the problem areas I first mentioned.
I tested charging the battery by connecting to my computer's USB port, and, although it is charging slowly, at least it's not discharging while connected.
I think that experience discharging while connected might have been because Opera 9.33 beta was open to a page the was running something - just speculation.
I think it's also possible that I misinterpreted what I saw; it might not have been discharging while connected; instead, it might have been a delay in updating the display of the state of the battery; when I looked at the battery when I first connected to the USB, it showed 70%, but in reality it might have only been 60% charged, and the display had just not updated; then, when I disconnected it, the display had updated to the correct 60%.
Also, I haven't noticed any of the extremely slow performance when open apps or running apps. I did notice that my old Kaiser is a lot snappier than the Athena before I updated the ROM. I'm going to keep an eye on it, and do some more Kaiser/Athena performance comparisons.
I think the Athena may be slower than the Kaiser because of the video driver issue. The Athena has four times as many pixels to render, and the CPU has to do the rendering since the driver that would take advantage of the ATI video processor is absent. Hopefully, that will be fixed soon, as mentioned at HTCClassAction.org. http://www.htcclassaction.org/
I am going to start a new thread on a couple of questions I have. In the original HTC ROM, there was a network program from HTC, and I used it to connect to shares on my LAN over WiFi, and I want to find a replacement for it. There may even be a network program in the Dual 3.0 ROM, but I haven't found it yet.
Also, I love MS Voice Command 1.6 (a version made available in the Kaiser forum - not a more recent 1.6 version for sale by MS.) It works for me on my Wizard and on my Kaiser, but on my Athena, I can't start Voice Command using my Bluetooth headset.
I've searched both of these issues in the forums, but haven't found answers yet. Again, if anyone knows, please help.
Now, I'm going to explore the 3.0 ROM!
Click to expand...
Click to collapse
To get MS 1.6 to work try this:
Delete the paird BT headset, then do a reset on the phone then re-pair with the BT headset. Make sure the headset is not set to (stereo) mode and that should work. I had the same issue with the Jabra BT8010. After doing the above steps the push button activation innitiated voice command.
Thanks TootTalk2000,
That worked. I have the Jabro BT8010 too.
Have you figured out how to get the BT to work hands free and stereo too?
xdafile said:
Thanks TootTalk2000,
That worked. I have the Jabro BT8010 too.
Have you figured out how to get the BT to work hands free and stereo too?
Click to expand...
Click to collapse
Yeah, when you set it to stereo however, all the audio gets routed to the BT headset (I personally don't like that, especially when using my GPS) and in order for you to use voice command then you have to take stereo/mono button which is the button closest to the mic on the bottom of the BT, then hit the answer button and you will hear VC prompting for your command. The draw back to this also is that everytime you want to use VC you will have to repeat these steps because the BT defaults back to stereo after you're don't with a voice call.
Hello all,
Not sure if anyone has had this happened to them as well.
I am looking to root the phone and this is the only thing holding me back in fears that would be a hardware issue and then can't replace. But thing that it is software.
Here is what happens, like in the mourning I will wake up and check time on device by just pressing lock once and put down (has happened even with out doing that) then will see that alarm won't go off and try and wake the phone with power button and will get no response from the device just black screen and phone is getting warm.
I will actually have to remove and reinsert the battery to get to come back on.
Has been doing this since the update. I have tried to go an uninstall all the programs I don't use and don't have anything on it that my mytouch is not running and that device has no problems. Tried master resetting the device a few times.
I have reset from the recover wipe data option and from spl neither seemed to help
Problem only seems to happen after the phone has been on for over 100 hours.
Weird thing I took notice is after a master reset it redownloads all the apps again right away. Don't know how to stop that.
Right now mine is running the stock software the shipped version manually update to official touch update from sdcard.
So my question is there anyway to have the phone keep the logs since logcat is reset when the phone is restarted to find the problem. Or if this something you all have seen. Any ideas would be appreciated.
Hopefully you have a software-only problem... and I don't know how to prevent logcat from resetting after restarting the phone... but I can recommend one possible solution...
1. Get the stock Google/HTC signed EPE54B firmware... http://forum.xda-developers.com/showthread.php?t=642811
2. Rename it to PASSIMG.zip, copy it to the root of your SD card.
3. Reboot in bootloader and select Bootloader from the menu. Your phone should start scanning for the PASSIMG.zip and ask you to apply the firmware update...
And, yeah... no you won't void your warranty by doing this, since this is a stock signed original firmware....
I get this (or a similar) problem too. I'm not yet sure if it's a hardware or software problem, and am therefore avoiding rooting my phone until I'm sure.
I have noticed that this happens more often, or at least seems to be more likely, when the phone is cold... I've not had it happen during the day (when it's nice and warm in my pocket), but when I leave it on my night stand whilst sleeping, or for an extended period on my desk at home, it seems to freeze up then.
I'm an electrical engineer and suspect that this problem may be due to silicon right on the edge of it's qualification range (similar to how some people are able to overclock to 1.2 GHz stably, mine is unstable even at 1 GHz... :-( ), I think my device is unstable at 998 MHz at whatever voltage it's running at currently (looks like Qualcomm changed the recommended voltage from 1.25 to 1.275 and finally to 1.3V over the course of early 2010).
See some of these commit comments for more details:
https://www.codeaurora.org/gitweb/q...it;h=6ede969b4418be5f8f2bd128d0cd4fbd3fd97e72
https://www.codeaurora.org/gitweb/q...it;h=ff61966464a2a2d2da36c0194d326370d3c3caeb
https://www.codeaurora.org/gitweb/q...it;h=a129aec2ec8b0b8ef9943e437415073620f15678
Based on them, I would guess we can expect more stability in the FroYo release (assuming it's using the 2.6.32 kernel, and is coming soon). In which case I'll wait.
I will try that rom next. In my tinkering I went back to erd and let it auto update to ere on its own. and will see how that does. If it fails again I will try the other rom. I can still revert back from that to erd if I want later right?
everything except the radio... i believe the radio can only be downgraded on an unlocked phone... so i've heard...
It happen to one of my nexus one too, the other one never hangs. It happen mostly when i'm charging on the dock with screen on.
I address this problem with HTC once, and they told me to try remove the micro sd card and see if it happen again. So i switch a newer sd into the phone and its running fine waiting to see if it hangs again if it does, HTC say will they come send a carrier over to fetch the phone to check it.
Running fine for 4 days already, just weird tho how can a sd card cause this?
Could also be a low memory issue with the stock ROM. My wife's does that until I kill a bunch of background apps. I look at the available memory and it's at 13MB. She also hasn't reboot her phone in weeks...so that's probably why it was low on memory. I guess the internal Android task killer doesn't do it's job very well!
I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?
chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!
Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.
cool, thanks. I'll try this today.
chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.
New NC w/1.3 did BN stock update to 1.41, confirmed all working. Then I applied the manual nooter 5-12-20 using CWM sd with no errors or issues in installing/rooting/booting. A couple issues/observations after successful booting.
Posting here as new user hoping other new users in same boat without enough time on forum to be allowed to post to the dev thread (I've read every page of the thread and every post since 5-12-20 was released mult times so can say these questions/observations are either not observed or observed and not definitively answered that I could find).
A couple observations and questions:
1. At least 2 other posts noting issues with WiFi.....mid-usage wifi just drops goes dead and I have to manually connect - only started after applying 5-12-20 - is there a fix or something more I can contribute testing?
2. Damned market. Seen many posts relating to market - some claimed to "fix" by re-rooting after going back to stock (doesn't make sense since I observed no errors in the process). My market launched, then updated fine. I, however like others saw many common apps simply not there like Google's own Voice app, facebook app, etc. Maybe someone can tell me, should my rooted nook color NEVER even see those 2 apps in the market? If it should, something went wrong. **Yes, I went back to page 1 of that thread and applied the "market visibility fix" which really needs to be updated to say you MUST uninstall the market "update" to roll it back to the original rooted market then apply the steps - then yes, it worked in the sense that all apps EXCEPT for some pretty BIG ones like facebook, google voice, etc are listed. This one is the primary reason I'm rooting and I've read a LOT of different "fixes" of changing DPI, fingerprint, build.props, etc. yet in any of the original root instructions seen an indication that this is a STANDARD action every rooter needs to take. Why do some need this "workaround" of hacking dpi and props and some don't? Is it simply that those that don't are not using these very common apps like facebook? Someone could make my day by helping out with this as I really hate doing things half-assed and having something half-working.
3. Power consumption seems a bit higher than pre-MN-root which leads me to next question - the MN rooting process installs "google latitude", "navigation", and what appears to be phone processes. Without a gps or location services I can't seem to get these nav type apps to work (hang at aquiring location), is there a reason they are installed and is there a way to make them work? Can any of the phone/dialer type daemons be removed could any of them be increasing power consumption? Again, I'm game for testing if a dev can shed some light.
4. Basic question but one I saw people had app "updating" issues with but no clear answer as to best practices. If an app is available in both BN store and android market, are there pros/cons to installing one vs other? Netflix good example installed via BN store yet market says update when BN store does not.
5. Dual-booting - seen different threads but they are dated to older firmware and with the awesome job GMPOWER did putting together 5-12-20 MN, would love to help him or the devs test and put together a step by step rolling his 5-12-20 MN and current 1.41 in with whatever the best practices are for setting up a dual boot with CM7, etc.
Again, you guys rock and I love the NC, any help on these would be greatly appreciated!
I'm new here too,but I might have a simple solution to question #1.If you're "dropping WiFi" at home,check the channel your router is using and see if a neighbor (or two or three)are also using that channel."Sniffer" programs are around that will give you the info.Try to set yours up on a "clear" channel.Worked for me when the neighborhood "filled up" with routers all set to channel 6.Went to ch.3 and problem solved.
Good luck.
Thanks but as I stated only after the manual nooter is the wifi dropping - no need to get out wireshark when 4 other wifi devices including a non-rooted nook in the same room without dropping but thanks for the suggestion!
BTW, I should ask are you rooted and which version, etc?
WyldWolf said:
[...] 1. At least 2 other posts noting issues with WiFi.....mid-usage wifi just drops goes dead and I have to manually connect - only started after applying 5-12-20 - is there a fix or something more I can contribute testing?
Click to expand...
Click to collapse
I did not experience this issue. In fact, on B&N 1.4.1, my wifi was more dependable than on CyanogenMod. I suspect a lot of has to do with specifics on your wifi setup, including router make, security used and so forth. You could try tweaking parameters to see if it helps. Was it dropping as much before you ran MN? I wouldn't expect what was done with MN to make a difference. Are you using Dalingrin's kernel or anything similar?
2. Damned market. Seen many posts relating to market - some claimed to "fix" by re-rooting after going back to stock (doesn't make sense since I observed no errors in the process). My market launched, then updated fine.
Click to expand...
Click to collapse
Hmm. I never got around to trying Google Voice, and have no use for Facebook, so can't say for sure those were there. I've since nuked 1.4.1, so can't test now either. I can say that I had well over 100 apps that I commonly use on CM loaded, and didn't find any that I weren't visible in Market without any tweaks. It did take a long time for Market to update, but after that, it worked smoothly. You might try accessing the Market via the web interface and see if those apps will install from there. I did that a few times. Maybe that trips something?
3. Power consumption seems a bit higher than pre-MN-root which leads me to next question - the MN rooting process installs "google latitude", "navigation", and what appears to be phone processes. Without a gps or location services I can't seem to get these nav type apps to work (hang at aquiring location), is there a reason they are installed and is there a way to make them work? Can any of the phone/dialer type daemons be removed could any of them be increasing power consumption? Again, I'm game for testing if a dev can shed some light.
Click to expand...
Click to collapse
My power consumption was initially very good, but after a week or so, I started seeing the battery drain go to 3-5% per hour. Unfortunately, 1.4.1 hobbled a lot of troubleshooting tools, so I wasn't able to nail down the culprit. This is what ultimately drove me to abandon 1.4.1 for CM again.
I did try renaming phone.apk and others that have been recommended, but my NC seemed to get very unstable thereafter. Lots of spontaneous reboots and the like. I put them back and really didn't see a big difference one way or the other that I can attribute to these. From everything I've read, they're not likely to cause noticeable drain, but some other standard functions depend on them.
4. Basic question but one I saw people had app "updating" issues with but no clear answer as to best practices. If an app is available in both BN store and android market, are there pros/cons to installing one vs other? Netflix good example installed via BN store yet market says update when BN store does not.
Click to expand...
Click to collapse
Cost is probably the main factor. Netflix from B&N supposedly supports HD while the Market version does not. On a 7 inch screen, I couldn't care less. Netflix off of the Market looks pretty good, so I'm happy.
5. Dual-booting - seen different threads but they are dated to older firmware and with the awesome job GMPOWER did putting together 5-12-20 MN, would love to help him or the devs test and put together a step by step rolling his 5-12-20 MN and current 1.41 in with whatever the best practices are for setting up a dual boot with CM7, etc.
Click to expand...
Click to collapse
What you do to stock is pretty much independent of dual-booting.
Bobstro,
Thanks so much for the input! As for the wifi, it does seem very specific to after I ran the MN on 1.41, in fact it never once dropped and I went back to stock 1.41 for the last day and haven't seen it drop again (my wife's is stock 1.41 and doesn't drop either when my MN does so unless it's a hardware issue I'm guessing it's something in the MN process, driver, etc.)
One weird thing I did have happen and searching found a couple references but nothing definitive was using CWM 3.2.0.1 flashing the 1.3 stock after formatting system, data, cache multiple times was my touchscreen did not work. I even re-downloaded the 1.3 from xda must have flashed 6 times never worked. Then downloaded a 1.41 posted on one of the recovery xda threads and lo and behold my touchscreen worked. Also, unlike the 1.3-1.41 upgrade, when I flashed right to 1.41 a couple things came up that didn't after upgrading mine and my wife's to 1.41, namely netflix right on the home screen touch to install, and the nook friends app right on the home screen.
Have you come across anything that would indicate why my touchscreen went dead no matter how many times I rebuild the CWM card, formatted the nook partitions correctly and flashed without error? It really made me worry I had a bad unit but like I said worked out of box, worked after 1.41 upgrade, worked after latest MN, only once I returned to 1.3 stock did it die until flashing 1.41 directly.
Interesting about the market, I did have thousands of apps just not some of the most common big ones and I did try through browser it told me facebook was incompatible with my device which led me to all the "hack the dpi, props file, etc." threads I just didn't want to be part of a minority for for some unknown reason had to hack workarounds if 99% of folks running the MN could simply install facebook and google voice from market without workarounds.
Thanks again!
Edit: on the dual boot I thought there was a way to install CWM or something to internal to allow dual internal booting from stock (nootered) and CM7 - I'll keep looking.
WyldWolf said:
Thanks so much for the input!
Click to expand...
Click to collapse
I'm happy to help where I can. The smart folks here on XDA have helped me tremendously, so I trying to pay it forward as best I can!
[...] One weird thing I did have happen and searching found a couple references but nothing definitive was using CWM 3.2.0.1 flashing the 1.3 stock after formatting system, data, cache multiple times was my touchscreen did not work. I even re-downloaded the 1.3 from xda must have flashed 6 times never worked. Then downloaded a 1.41 posted on one of the recovery xda threads and lo and behold my touchscreen worked.
Click to expand...
Click to collapse
EDIT: Sorry about that strange post. I wanted to point you to the thread about the hardware having changed with more recent NC versions. 1.4.1 includes the newer drivers. Depending on where you get your older versions from, they may or may not work.
Well that 'kinda" makes me feel better that I at least don't have bad hardware, had I known the 1.3 that's posted was "different" then the 1.3 that came on my newer unit apparently must have had the newer screen drivers I would have backed it up - surprised someone hasn't posted it. I mean, mine came with 1.3 installed and the screen worked so it must have had the newer driver until I wiped it, right?
Also, do you have the links you referred to for the screen issues thread?
Thanks again!
The ongoing discussion I referred to is here. On page 2 or so, I've got a link the the original post.
HimWill said:
I'm new here too,but I might have a simple solution to question #1.If you're "dropping WiFi" at home,check the channel your router is using and see if a neighbor (or two or three)are also using that channel."Sniffer" programs are around that will give you the info.Try to set yours up on a "clear" channel.Worked for me when the neighborhood "filled up" with routers all set to channel 6.Went to ch.3 and problem solved.
Good luck.
Click to expand...
Click to collapse
Do look at WiFi, Once I Locked it on channel 1 it is rock solid reliable.
Bobstro,
I'm guessing your battery life must be a typo, at 10% an hour discharge would be 10 hours of runtime - they advertise 8. 3-5% sounds awfully low. Mine out of box is at about 10% an hour with wifi on and screen at 30% with constant online web browsing, maybe an app or two install, launching in and out of system apps, etc. - constant "activity" on my part not just flipping book pages or watching a video, etc.....I hope my unit is on par with others.
I also noted that my wife's refurb bought about thanksgiving that does not have the "new" screen hardware mine does actually looks side by side more blue/white with mine slightly yellower tinge which annoys me a bit. I know from years of jailbreaking and swapping iphones that there was definitely a difference in screen colors as they went from the 3g to the first 3gs I had, same thing blueish/whiter to a more yellow tinge - I can't win! LOL
Ah, sorry for the ambiguity. That was 3-5% while idle with screen off, which is far worse than normal. I expect to see 4-6% drop while idle with screen off overnight, max.
While in use, consumption is roughly 10% per hour, and mostly due to screen, which I usually run at 25%.
Downloading now, clocks in at 691.01 MB
Enhanced SHIELD Hub Features
Network Test capability
User Customizable " My Android Game" and "My Media Apps"
Improved Touch Performance
Misc. Stability and Localization Improvements
Will let you know how it goes.
Do you still have root after updating? That is all I want to know before I update.
SuperSu was unable to preserve root, but Towelroot still works.
technoviking said:
SuperSu was unable to preserve root, but Towelroot still works.
Click to expand...
Click to collapse
691MB means that most likely, the update is fully wiping /system and redoing everything.
The benefit of doing a full deployment instead of a delta is that while it uses up MUCH more network bandwidth, at least it is far less likely to fail.
Screen lag is no better for me, unless I use max performance.
Sent from my SHIELD Tablet using XDA Premium HD app
This update fixes the problem of embedded Youtube videos not playing in Reddit apps and things like the Play Store.
karehaq said:
This update fixes the problem of embedded Youtube videos not playing in Reddit apps and things like the Play Store.
Click to expand...
Click to collapse
This is definitely a big plus. I wonder if Tapatalk will work after this update.
I wasn't expecting much from this update to be honest, "Misc. Stability and Localization Improvements" doesn't really give any information about what has been fixed...
I can however report that it has fixed my two biggest issues so far (admittedly this is only after two days of testing).
I haven't had a single SoD since the update compared to one every time the tablet was unused for more than two hours. This was reproducible every time on my tablet; 1:59:00 tablet would turn on without needing to do a hard reboot, 2:00:01 tablet wouldn't turn on necessitating turning it off by holding the power button for 10 seconds and then switching back on. I've now been able to turn the tablet on after leaving overnight for the last two nights
It also appears to have reduced the battery drain (maybe related to the SoD who knows...) when the tablet screen is off, instead of the battery stats showing a constant downward slope it's now a pretty much flat line while not being used overnight.
Again this is obviously early days but it's definitely made a difference to my particular tablet YMMV.
Guys, is it better to update or not? I have root and alot of games , Is this update will wipe and effect on my data?
LG G Pro2 - tapatalk
How do you block/prevent OTA updates on the Shield Tablet?
You can update whit no problem, you are not going to loose any data, but you will loose root access, but use towellrot to gain access again.
Sent from my SHIELD Tablet using XDA Free mobile app
SoD still there. This problem is killing me
What exactly is this problem ( SOC)
Sent from my SHIELD Tablet using XDA Free mobile app
rene130313 said:
What exactly is this problem ( SOC)
Click to expand...
Click to collapse
I assume you mean SoD?
Sleep of Death; the tablet won't respond to any attempts to wake via the power button after it goes into deep sleep. This used to happen to my tablet after two hours every time. The update appears to have fixed my tablet I still haven't had any issues since applying it.
Still having the weak wifi issue when holding the tablet in portrait mode at the bottom, though I'm hoping when my case arrives that will resolve the issue as it did for my iPhone 4 back in the day...
Llarrinye said:
I assume you mean SoD?
Sleep of Death; the tablet won't respond to any attempts to wake via the power button after it goes into deep sleep. This used to happen to my tablet after two hours every time. The update appears to have fixed my tablet I still haven't had any issues since applying it.
Still having the weak wifi issue when holding the tablet in portrait mode at the bottom, though I'm hoping when my case arrives that will resolve the issue as it did for my iPhone 4 back in the day...
Click to expand...
Click to collapse
Adding my case definitely helped some with the wifi drop, though didn't knock it out totally. SoD occurs quite often on my LTE replacement where it didn't happen as often on my wifi only I RMA'd. Factory resets and even no apps installed doesn't change the crashes and SoD issues. Even coming out of console mode it seems to do it 70% of the time requiring reboots to fix. Its almost comical how many crazy issues this tablet as a whole is having out the gate.
I have had zero SOD since upgrading to 1.2. Stinks that it is still happening for some though.
I think it is a hardware issue they are not admitting. I finally call NVIDIA support today to describe the lag and SOD I'm still having with 1.2 and was given a RMA without asking for one.
How do you flash the image files? I just didn't get the instructions from nvidia website. Can someone clarify everything on how to install the update using PC or using recovery? Ta..