Related
Let us track the OPEN issues on Android HD2, we will only discuss problems dealing with android alone, issues arised due to radio, WinMo rom and a specific android rom should be ignored.
AFAIK we still have 3 main Problems
1. GSensor/ Touchscreen Freeze.
Related Files in Android : \system\bin\akmd,\data\misc\AK8973Prms.txt and \system\lib\hw\sensors.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
This issue is not noticeable unless you a play game which uses Gsensor (Eg Abduction, NFS Shift ...)
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=803242
Possible Workaround :
1. Disable Auto-Rotate screen in Settings -> Display
2. Run the following commands in Terminal
mv \system\bin\akmd \system\bin\akmd2
killall akmd
To Restore
mv \system\bin\akmd2 \system\bin\akmd
Basically you are renaming the file 'akmd' which is responsible for the sensor to work
2. Data Disconnects
Related Files : \system\lib\libhtc_ril_wrapper.so
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=794309
Possible Workaround :
1. Switch Mobile Network OFF and then ON (Add a widget [Widget -> Settings -> Mobile Network])
2. Switch Airplane Mode OFF and then ON (Add a widget [Widget -> Settings -> Airplane Mode])
[EDIT]:
Guys looks like we got a fix.. this wrapper seems to work flawlessly as of now... you can try it here...
http://forum.xda-developers.com/showthread.php?t=824413
Just download 0.3 file and replace the file at /system/lib using root explorer
3. Occasional Black SOD and Accuracy in Auto Brightness
Newest kernals seems to have this issue, where the display stays black while the keypad lights glow.
Related Files : \system\lib\hw\lights.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
Possible Workaround :
1. Show the Sensor of your phone to some bright light source and your display will be back
2. Disable Automatic brightness in Settings -> Display-> Brightness
I will update this thread with Solutions as and when the developers fix it.
Whatever i have written is limited to my knowledge, it could be wrong, if so please correct me, Most of the vetarans know these issues and the work arounds, i have just put everything together for the new comers and to remind the developers of the existing bugs
Mods feel free to move the thread to General if need be.
Hi depakjan, This is great, thanks for tracking these issues.
can people confirm this "occasional bsod"?
i haven't seen it since light-sensor is calibrated.
i think the bsod is fixed with 2.12 radio and above..
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
depakjan said:
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
Click to expand...
Click to collapse
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I second that explanation ... and the auto backlight levels in CM builds may actually work better than Desire builds if tweaked properly... atleast for me the reaction time of the sensor is much faster ... accuracy still a problem
Accuracy is still a problem, so is Black SOD .. i have been getting this in Mdeejay's Revolution, HD .. latest ones...
it so happens when you have been talking over your phone for a long time(which blocks the sensor from light).. and then when you are finished with the call it wont wake up... maybe it did not sense light ... but after you show the sensors over a bright light source.. it comes back..
i have seen couple of posts and users mentioning about this...
lets see if everyone agrees that there is no Black SOD, i will modify the post for accuracy..
Support of HTC extended battery
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Can we also add tracking of Idle / Screen Off Battery Drain? Target is 5-8ma, some builds run at 100ma.
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
badmonopoly said:
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
Click to expand...
Click to collapse
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Led Notification is not functioning, especially on Sense build.
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
jcc266 said:
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Click to expand...
Click to collapse
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
hastarin said:
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
Click to expand...
Click to collapse
. . . can I just 'tip my hat' to you hastarin . . . you 'd' man
And I'm hopeful that all the devs and chefs will have these problems solved before too long.
Viv la HD2 Android!
Reno_79 said:
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Click to expand...
Click to collapse
What doesn't make any sense is that the app successfully downloads, but either stalls when it needs to d/l or tries to install and tell me it was unsuccessful.
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I've found the backlight problem occurs (generally) if I unlock/lock the phone fairly quickly in a short space of time (and yes, I've only seen this on Hyperdroid 1.6 & 1.7, both CM6 builds). It's not consistently reproduce-able though, I can go several days without it happening, then have it happen a couple of times in a single day.
The touch screen is still active though, and swiping the unlock brings the screen back to normal brightness levels.
Tyrion84 said:
Led Notification is not functioning, especially on Sense build.
Click to expand...
Click to collapse
Works for me..could be your build ....try some other build...
hoss_n2 said:
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
Click to expand...
Click to collapse
this is already covered in the third point as accuracy
Works for me..could be your build ....try some other build...
Click to expand...
Click to collapse
Hi!
I wonder what "works for me" means. What exactly are your leds doing? On all builds i tried so far the left green led flashed about one time a minute green and nothing happened when the phone was charging. Are there some hidden settings or a special program for hd2 leds?
Cheers,
Otto
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.
["Somebody's" CM10 & "That" rom] Bug/fix reports & newest info (26-Oct-2012)
Firstly, I would like to give a big Thanks to "somebody" as well as the dev team at the behind of these roms for their efforts to bring ISC & JB as great things to our device.
Recently, I've tried both the ICSROM (known as the tune of leaked Rom under CWM flashable zip - Let's click Thanks for Upndwn4par) and "somebody's" CM10 (let's click Thanks for ticiano_arraes) and saw that they both have identical issues as reported by people such as the battery life, the deep sleep, the camera flash... including working fixes. But the fixes spread over the pages of threads caused inconveniences for us to track or update info. So I would like to open new thread just for purpose of collecting bug reports and the fixes from and for both users and our devs to get latest info on these roms quickly.
Admins please feel free to delete if this thread is already opened or if it's just not neccessary.
Belows are lists of great things of ICS/JB given by these roms that you can taste right now, and also the list of bugs/issues along with the best possible solutions that you can try for workaraound while waiting for the perfect release. The lists will be updated upon report from you guys. So please provide any thing from your experiences on these roms.
* Great things:
** For both roms:
+ Touch sensitivity is a big improvement in speed and accuracy (this might be inherited from Butter Project)
+ HDMI mirror works fine.
+ Others (pls share your experiences...)
** Individually for each rom:
ICSROM:
+ Webtop 3.0: work like a charm!
+ New Camera/Camcoder by Motorola with various valued upgrades such as Auto continuous (live) focus mode even for camcoder, full HD capture...
+ FingerPrint scanner @first steps of working (worked but not yet supported by original ICS/JB).
+ New valued apps added, such as Smart Actions (similar to Tasker, Locale but more intuitive/friendly/efficient), MotoPrint (valued add not only for business man but even for home usage), Battery Tracer (for battery monitoring with rich info)...
"Sombody" CM10::
+ All great things from CM10 as you experienced with such as Epinter's rom...
+ Camera/camcoder: worked.
+ 2D hardware accelerator: worked.
+ Data/GPS/Wifi/Bluetooth...: worked fine.
* Bugs/issues and workarounds (Newest update info are sized in big text, this helps you guys to track info more quickly):
1. Camera flash doesn't work properly: (Fixing is in progress...)
- Temporary solution: Turn on the torch while capturing in dark (shouldn't keep the flash on continuously over 5 min for safety of the LED flash light)
2. Deep sleep problem (which causes your phone cannot wake up upon power key pressing): CM10 23-Oct build FIXED. But some users reported that the bug is still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
If this problem still persists on your Atrix, try one of solutions belows:
- Solution 1 (confirmed): Remove the external SD card.
- Solution 2 (Edited: seems not worked): Turn off any screen unlocker (Choose None in Screen Unlock Options)
- Solution 3 (needs more confirmation): Just reboot your phone once or serveral times after rom installation
- Solution 4 (provided by Pont91-unconfirmed):
+put all media files on internal SD;
+deleted all files created by any app on the external SD;
+set internal storage as main one for all the apps data (downloads, photo, rec, backups, etc.).
- Solution 5 (worked with many users): Set Never for Screen Timeout in Settings/Display, remember to press Power button to turn off the screen instead
3. Randomly reboot issue: (the phone suddenly reboots for unknown reason):
- Solution 1: (need more confirmations): Remove the SD card.
- Solution 2 ("Somebody's" CM10) : (need more confirmations): Turn off Wifi :cyclops: There are two guys who provided that:
+ Either turning off Wifi
+ Or set Wifi to NEVER SLEEP (Always on) by: Settings/Wireless & Networks/Wifi Settings/Advanced/Wifi sleep policy
can help stopping reboots. Not only for this problem, but even the issues of heat and deep sleep can also be improved. From their reports, it seems that there is some problem related to the Wifi driver with "those libs". So, try this solution at your own case and help our devs by confirming this way again. Tks.
4. The heat issue (the phone seems to keep hot all the time): The issue seems to walk along with the deep sleep problem, so the issue may be cleared when the fix for deep sleep is applied.
5. The battery life: So bad
Both ICSROM (known as the leaked ICS) and CM10 with "those libs" have an identical problem of battery life. As shown on my phone, the battery drains from 100% downto 50% just after a couple of hours in usual use, even if your phone is in idle state.
No fix yet for this issue But you can apply some of following improvements:
- Lock (freeze) unnecessary AT&T apps and services (ICSROM only)
- Turn off Auto Syn (Manually mode instead)
- Turn off or lock all tracking/reporting sevices you doubt
- Use static wallpaper instead of live one
6. Ram low or several other suggestions only for ICSROM: clike here
7. The I/O performance is a characteristic weakness of both roms which are using "those" libs. You can see this on the results report of Quadrant. Essentially, you can see that the data processing speed is significantly slower than the CM7.2 by using, for e.g, Call Log Backup & Restore, etc...
No yet improvement for this disadvantage of both roms
8. Blackscreen issue after a lock/unlock: CM10 23-Oct build FIXED. But some users reported that the bug is now still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
9. Black incoming call screen and blackscreen issue after a call: CM10 23-Oct build FIXED. But some users reported that the bug is now still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
...Other issues (please share and provide your own solution...)
Thanks for continuous reports from you guys!
(To be updated...)
flusshd said:
Firstly, I would like to give a big thanks to "somebody" as well as the dev team at the behind these this rom for the efforts to bring ISC & JB as great things to our device.
Recent days I've tried both the leaked Rom and "somebody's" CM10 and saw that they have the same identical issues as reported such as the battery life, the deep sleep, the camera flash... and some working fixes. But the fixes are spread over the pages of threads that cause inconveniences for us to track or update. So I would like to open new thread for collecting the bug reports and the fixes from and for people to provide quick update info on these roms.
Admins please feel free to delete if this thread is already opend or is not neccessary.
Belows are lists of great things and also the bug reports along with the possible or even just temporary fixes that you may should try to resolve. The lists will be updated upon report from you guys. Please provide any thing from your ecperiences on these roms.
* Great things:
+ Camera/camcoder worked.
+ 2D hardware accelerator worked.
+ Data/GPS/Wifi/Bluetooth... worked.
+ FingerPrint scanner @first steps of working.
+ Touch sensitivity is excellent (this might be inherited from Butter Project)
+ Others (pls share your experiences...)
* Bugs and most likely fixes:
1. Cammera flash doesn't work properly: No any fix yet.
2. Deep sleep problem (which causes your phone cannot wake up upon power key pressing):
- Solution 1 (confirmed): Remove the external SD card.
- Solution 2 (unconfirmed): Turn off any screen unlocker (Choose None in Screen Unlock Options)
3. Reboots issue: No solution yet.
4. The heat issue (the phone seems to keep hot all the time): The issue seems to walk along with the deep sleep problem, so the issue may be clear when the fix for deep sleep is applied.
5. Other issues (please share and provide your own solution...)
Thanks in advance for continuous reports from you guys!
Click to expand...
Click to collapse
Thanks For your report!
My phone is an US AT&T. Installed ICSROM yesterday (WOW!!!) and confirm what you posted.
Biggest bug is the battery. It seems to consume 1% every minute! In an hour I was down to 40% after full charge and using Play Store on wifi. Webtop/Mirror mode works awesome! Watched some HD videos and listened to some music... all good. After using the HDMI connection, I confirm that you will not get black screen until you reboot the phone. Turning off any screen unlocker does not fix the deep sleep bug. 1 reboot. Overall, it is very good.
Keep up the great work and thank you for your efforts! :highfive:
flusshd said:
* Bugs and most likely fixes:
1. Cammera flash doesn't work properly: No any fix yet.
Click to expand...
Click to collapse
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
gkarthik16 said:
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
Click to expand...
Click to collapse
Thanks for the suggestion !
gkarthik16 said:
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
Click to expand...
Click to collapse
It works
Anyway, it seems i've stopped deep sleep reboot, with external SD inserted, in this way:
-put all media files on internal SD;
-deleted all files created by any app on the external SD;
-set internal storage as main one for all the apps data (downloads, photo, rec, backups, etc.).
Hope this can help you in some way
Sent from my beloved Atrix
Android03 said:
Turning off any screen unlocker does not fix the deep sleep bug. 1 reboot. Overall, it is very good.
Click to expand...
Click to collapse
Really this fixes the deep sleep bug? Have you made tests for a long time of usual use? Pls confirm.
Can anyone else confirm this fix again?
First of all, thanks for the report.
Regarding the FP reader - what's really working and what isn't? Could someone enlighten me there?
As I'm back to cm7 right now, I would like that if you find any bug/fix, PM me. I will put it on the OP in the dev section.
Oh, btw, the flash workaround was my idea
I heard removing the SD card fixes the reboots.
Sounds like this might be similar to what pont 91 talking about.
Is there any fix for the upside down front camera in "somebody's" cm10?
Sent from my MB860 using xda app-developers app
Not sure if this is a bug with the roms (Somebody's 10/19), but I'm not longer able to track total data usage on my phone. Some apps will show the amount used by individual apps, but none will actually total it up (They all say 0 total data usage).
Woah where you getting October 22 from???
Fixed
flusshd said:
Really this fixes the deep sleep bug? Have you made tests for a long time of usual use? Pls confirm.
Can anyone else confirm this fix again?
Click to expand...
Click to collapse
deep sleep fixed;
Fixed blackscreen issue after a lock/unlock
Fixed black incoming call screen and fixed blackscreen issue after a call
mediafire . com / ?p3cl9j16v828i6y
cm-10-20121023-UNOFFICIAL-olympus.zip
israelborges said:
deep sleep fixed;
Fixed blackscreen issue after a lock/unlock
Fixed black incoming call screen and fixed blackscreen issue after a call
mediafire . com / ?p3cl9j16v828i6y
cm-10-20121023-UNOFFICIAL-olympus.zip
Click to expand...
Click to collapse
So, no more random reboots?
quetzalcoatl2435 said:
So, no more random reboots?
Click to expand...
Click to collapse
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Antieco said:
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
from here
http://forum.xda-developers.com/showthread.php?t=1934662
quetzalcoatl2435 said:
So, no more random reboots?
Click to expand...
Click to collapse
I'm trying it right now. I'll let you know
Antieco said:
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
quetzalcoatl2435 said:
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
Click to expand...
Click to collapse
Have you tried it? Can't stand black screen after call!!!
Sent from my iPad using Tapatalk HD
quetzalcoatl2435 said:
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
Click to expand...
Click to collapse
Yes, but it's not the first time he did this
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
Never had one so far. Running stock 4.2.2/Franco kernel nightly_110
-Edit- currently undervolted -75 mV.
just stop messing your phone up with stupid OCing and benchmarks... This issues are installed to protect the hardware from crashing... ( Red light of death... )
My phone just fine. never had this SOD.
Never had an issue on this device. On my old phone, dropping the min CPU speed too low would cause it a LOT.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
You don't have an option for unable to turn on phone without a reset: no blinking led. This is also a scenerio.
Please take a look here! http://forum.xda-developers.com/showthread.php?t=2195278
I've tried almost everything (wipe& re wipe , install stock ) and nothing seem to solve it.... most frustatin thing is when I hit "home" after playing heavly and ...bamm it goes black screen & hav to reboot pressin home&vol+
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Im using it now (customROM&UV) since it doesnt affect my issue.... I tried completly stock for 2 days and keep crashin... or at least on g.earth as I didnt install any app/game to be sure its not an app related issue.
Cant figure out what happens, it can play games w/o any issue, but sometimes when I change orientation it just goes black
PD: I dont hav enough time, but ill do a logcat to see what can possibily make it freeze
My case is not listed in the poll options:
- the phone went into standy, good battery, no calls, no high loads;
- LED was inactive totally.
- then I was unable to turn it on normally (only through reboot).
While in this state, trying to call the phone resulted in "long" tones, i.e., like the network saw the phone. The phone did not ring.
This happens with the latest stock firmware on the 2nd day of my use. Non-reproducible. Phone returned.
Would be delighted to learn if that's a hardware or software issue
Not necessarily SOD but experienced extreme battery drain under these situations
1- Charging via USB and left phone connected after PC shut down.
2- Charging via Wireless Charger left it on the pod.
In 1st ASA pc is shut down
and
In 2nd ASA Phone charged completely , as I suspect the charging process goes backwards ! It someone drain current from your battery to the power source.
AFAIK none of these issue are positive with normal good old AC charging. However you can still use a workaround by using the app called "Safe Charge"
This is my experience
Received the January security patch today. Haven't found any bugs yet.
There are no new bugs for me as well but the current one remain like the cache one. But my phone's performance has definitely improved a lot. It's finally quick now and I have not experienced any lags since 2 days.
Slow emmc, auto brightness won't go below 19%
no notification from download manager
Front facing camera flash isn't working
viniciusvm1 said:
Front facing camera flash isn't working
Click to expand...
Click to collapse
flash is working over here
LucasBarrios11 said:
flash is working over here
Click to expand...
Click to collapse
Same here, except the fact that the flash stays on for the whole time when I switch to the front cam.
[email protected] said:
Same here, except the fact that the flash stays on for the whole time when I switch to the front cam.
Click to expand...
Click to collapse
same here but i thought that's the normal behaviour
Unreliable data connection, after the latest update my phone has been dropping data connection constantly, especially when the screen is off. It could be my ISP, but it started right after the update, before it was working fine.
When will they fix the cpu the 4 core min freq is 1401 mhz it should be 633mhz. .need to restart the phone to fix it but after some time problem shows up again
When increasing or decreasing the volume sound, the window doesn't disappear automatically till I touch other part of the screen
Front flash not working
Emmc not fixed
Headphone volume not fixed
And some users facing bootloop after updating
So looks like the update is pretty good ?
---------- Post added at 12:54 PM ---------- Previous post was at 12:49 PM ----------
@viniciusvm1 It wasn't working for me but clearing the data for camera app fixes the issue
Notifications suddenly going mute and doesn't work untill I restart the device. The ringer is not affected though. I have seen this bug right after attending a call, sometimes with bluetooth headset paired . ( Don't know if that's causing it, but everytime I encountered this was after a call.) It used to even happen earlier at times... Does anybody has a fix for this? Anybody esle experience this? Thanks in advance!
They have pulled the January update.
psichokillah said:
They have pulled the January update.
Click to expand...
Click to collapse
Do they really not test the update before releasing it?? This was very sloppy and unprofessional and I can't believe an Android One phone experienced something like this, since it's backed by "Google" and whatnot.
No wonder many of the bugs are still unfixed, this feels like the development team is probably made up of one or two developers who have 13 other projects in parallel.
Shame.
psichokillah said:
They have pulled the January update.
Click to expand...
Click to collapse
Even after releasing the 'January Update' at the end of the month, they had to stop the updates? Damn. Imo, they are focusing too much on MIUI and not on Android One.