This topic will be posted and discussed bugs CM7.2 by FAT. I did not give a GitHub bugtracker because the mode is more convenient forum to work with users.
Bugs:
1. massive battery drain.
2. camera goes darker when switching to video mode, and still dark when switching back to photo mode. need to close and reopen camera to make it normal again
Total bugs:
2
Torch is not functioning, the Toggle LED Flashlight option is greyed out in Cyanogenmod Settings/ Interface/ Notification power widget/ Widget buttons.
its 1 bug not 0.5
Sent from my GT-S5830 using xda premium
kevinlekiller said:
Torch is not functioning, the Toggle LED Flashlight option is greyed out in Cyanogenmod Settings/ Interface/ Notification power widget/ Widget buttons.
Click to expand...
Click to collapse
Torch is working Oh u mean to say toggel prefrence is not working rite Under cynagoen settings rite
nice initiative.
btw bugs from previous/other cm7 version that still plague later build including yours
1. massive battery drain.
2. camera goes darker when switching to video mode, and still dark when switching back to photo mode. need to close and reopen camera to make it normal again
Latest Google Maps not working (according to reports, haven't tested), this is an important app!!!
A Github available so you can share your code. Android is open-source, and it is important that you share your fixes with the community, not just compile "closed" ROMs!!!
iandol said:
Latest Google Maps not working (according to reports, haven't tested), this is an important app!!!
A Github available so you can share your code. Android is open-source, and it is important that you share your fixes with the community, not just compile "closed" ROMs!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1484542 this version works.
If the phone is locked and I receive a message, when I unlock the phone to read the message, the soft keys blink once. how can I fix this?
an0nym0us_ said:
nice initiative.
btw bugs from previous/other cm7 version that still plague later build including yours
1. massive battery drain.
2. camera goes darker when switching to video mode, and still dark when switching back to photo mode. need to close and reopen camera to make it normal again
Click to expand...
Click to collapse
Massive battery drain sorry dont mind but the battery is good as far as i concern and some people also report that its having good battery life on my own experience i even noticed it is good not best ya compared to other CM version it is good
And I have problem with camera darkness plus vol up/down buttons not work for zooming (I set them in Advanced Options). Tethering not works too.
an0nym0us_ said:
nice initiative.
btw bugs from previous/other cm7 version that still plague later build including yours
1. massive battery drain.
2. camera goes darker when switching to video mode, and still dark when switching back to photo mode. need to close and reopen camera to make it normal again
Click to expand...
Click to collapse
Same here..And I don't know why CM touch screen sensitivity always have different 'feel' compared to stock ROM, without notice I'm always touch the screen more tightly to prevent miss touch. I think you guys understand well
Ps. Since this ROM is nearest to official then I'll tell more CM bug:
The bass sound's ugly than stock. You can check with mort player with same equalizer (without DSP mgr of course). Also the equalizer freq change from 5 freq (stock) to 6 freq (CM) and if you slide bass booster on mort, the sound more awkward
Um..oh. Laggy gallery! LOL
Sent from my GT-S5830 using Tapatalk
alex0296 said:
If the phone is locked and I receive a message, when I unlock the phone to read the message, the soft keys blink once. how can I fix this?
Click to expand...
Click to collapse
Not only for messages but when someone is talking to you in WhatApp and others, with all notifications. I think this is to warn you that something happened when the phone was in standby. It's not a bug imo.
The same thing happens with others CM7 roms that I've tested and the AOSP too.
but until you use them do not light. remember that in another CM7 ROM, this does not happen if I went to Settings-> CyanogenMod-> Interface-> LED Notification, except that in this rom, there is no menu Led Notification
is a very good rom but i have a problem, i test smartass, v2, conservative and never enter in deep sleep always 245mhz (my min frequency).
ps: sorry my bad english.
alex0296 said:
If the phone is locked and I receive a message, when I unlock the phone to read the message, the soft keys blink once. how can I fix this?
Click to expand...
Click to collapse
That is common..
Market does not get updated to the latest version. In earlier CM versions, it used to get updated.
Market.
*edit Fixed the problem with market icon
Great ROM so far.
text messaging touch goes rumbled, maybe coz of sensitivity... hope to fix it on next release :clap: more power to Frozen Ace Team...
After two days of usage, I would like to report that this ROM has battery drain issues. Much more than the vo-1 version of CM 7.2
wifi?
Wifi does not work for me. It doesnt scan. When I turn it on in the notifications bar it just turns itself off again after a minute or so.
In the settings the same thing happens. (sometime here it even force-closes)
I found this in the ROM-Thread (http://forum.xda-developers.com/showthread.php?t=1263292):
"
Originally Posted by MrChaosDesire
Hmmm. Wifi does not scan. Maybe a reflash might work.
<3 CyanoAce 7.1
Wi-Fi works fine, but when you turn it ON you can`t see all points, as on stock FW. You must go to the Wireless setting and insert your password there."
When I tried several times to type in the password and SSID it still didnt connect and just turned wifi off again.
Unfortunaly, this link http://forum.cyanogenmod.com/topic/41455-cyanogenmod-7172-samsung-galaxy-ace/ does not work for some reason. (maybe just my computer...)
just checked, it worked: link is not helpfull
Related
I've put this in the Development section because whilst it is almost fully functional, it still needs a lot of development. Please be aware of this when you download it. I am not to be held responsible for anything that may happen as a result of running this app.
Requirements:
Root Access & a Custom ROM (StreakDroid 1.8.0 recommended (CONFIRMED WORKING ON 1.8.0))
Built under a 2.2 framework. If you are running anything pre-2.2 please be aware it may not work.
Please remember to remove all previous versions of the app before installing.
Simply open the app and press the "Menu" button. I hope you can figure the rest out! Enjoy!
"LED Notification FREE" has been uploaded in the Market. It has full functionality and it Ad Supported.
Please be aware that this version includes an "AdBlocker Check". This will block the app from opening if you have an adblocker installed on your phone. Sorry about this but i hate adblockers Alternatively, you can just remove all instances of Admob from your Hosts file.
Code:
[I][B][COLOR="blue"]QUICK HANDCENT FIX[/COLOR][/B]:
Open Handcent, press 'Menu > Settings > Notification settings > Popup settings'.
[B]MAKE SURE[/B] 'Screen on for popup' is [B]UNCHECKED[/B].
Handcent wont interfere with my app from then on :D[/I]
NEW TO 2.0.1
Asks for SU Access when the app first loads Fixes some weird error that happens every now and again.
Completely re-coded the SMS receiver. Much smoother now!
SMS and Gmail Notifications can be turned on or off
New settings page - done properly now, wont save anything to sdcard [you can delete your STREAKLED folder now!] Press the 'menu' button when you open the app for settings.
Permissions tweaked (should be less LED problems)
KNOWN BUGS
Changing orientation during the pattern causes problems. Just don't do it!
Notifications overwrite each other. So if an SMS message arrives and then a Gmail, only the Menu button will be lit, and vice versa.
Services cannot be stopped (only by uninstalling) FIXED - 2.0
Sometimes all the buttons will end up being lit, not sure why. [SHOULD BE FIXED]
TODO
Add options for turning the SMS and Gmail notifications on and off DONE - 2.0
Have different patterns for each DONE - 1.3
Improve the UI (sort of) DONE - 2.0
Improve the pattern flashing sequence (sort of) DONE - 2.0
Clean up the code (WIP )DONE - 2.0
Fix orientation issue
This will ALWAYS be available for free on here, on Modaco and on my website (see sig) but i have uploaded a 'donate' version on the Android Market Place priced at £1.50, just incase you fancy buying me a beer
Enjoy
Meltus said:
I've put this in the Development section because it is not fully functional and still needs a lot of development. This is basically a proof of concept app.
Requirements: Root Access (tested on 2.1 but build under a 1.6 framework so it should work on 1.6)
All you have to do is run the application, hit the home button and receive a text (or send yourself one). If your phone is locked it will wake up and dim the screen and flash the home/menu/back LEDs in a nice pattern and then keep the screen dimmed until you unlock the phone manually.
The only problem is that you will receive a Force Close error message and you will then have the re-open the app for it to work again. I am trying to fix this but will not be able to look into it for a few days so i thought i would release what i've done so far.
I will be adding settings and more patterns as soon as i can fix this FC error.
Enjoy
Click to expand...
Click to collapse
Well... GREAT!!! Thanks! It works... Was searching this kind of app for weeks. Thanks again!
Great little app. Can't wait for thenext update
Nice work.
Just out of interest though, what's the dangers of having the screen on dim all night if I get a text message at stupid o'clock?
Wouldn't want to burn anything on my screen if that is possible.
Amdathlonuk said:
Nice work.
Just out of interest though, what's the dangers of having the screen on dim all night if I get a text message at stupid o'clock?
Wouldn't want to burn anything on my screen if that is possible.
Click to expand...
Click to collapse
Screen burn is an issue on LCD screens, hence why i set it to do a dim wake lock instead of a full brightness one. Saying that, i have absolutely no idea whether screen burn would still occur but ill test it tonight and report back
On a positive note i have fixed the FC error and will release the fully working version tomorrow!!
Nice work dude ! Look forward to a full release tomorrow.
Any way to make this compatible with non rooted steaks on 1.6?
Sent from my Dell Streak using XDA App
jdmnash said:
Any way to make this compatible with non rooted steaks on 1.6?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
No, i'm afraid not.
Without Root Access it will probably just force close.
Currently in the process of adding more LED patterns
It also now wakes the phone, unlocks the phone and displays an "SMS Message Received" popup which it then hangs at until you close it.
Do you guys think this is better or should I make it lock the screen instead?
What else should i add/change?
Meltus said:
Do you guys think this is better or should I make it lock the screen instead?
What else should i add/change?
Click to expand...
Click to collapse
I'd prefer it stayed locked, also if I read this thread correctly, it leaves the screen on (but dimmed?) is that true? I would need it to kill the screen, because as noted, it could kill your battery if you went a long time w/o clearing the alert.
Nice work so far though...
a042349 said:
I'd prefer it stayed locked, also if I read this thread correctly, it leaves the screen on (but dimmed?) is that true? I would need it to kill the screen, because as noted, it could kill your battery if you went a long time w/o clearing the alert.
Nice work so far though...
Click to expand...
Click to collapse
Yeah, that's the only problem.
unfortunately, killing the screen freezes the LEDs in whatever state they're in, completely defying the point of the app
What i could do though, is wake up the screen, flash the LEDs but leave one on and turn the screen back off. This would turn everything off apart from that 1 LED and you could use different LEDs for different notifications. I'll try that out later.
Yeah, that seems like a good idea. Maybe the Back LED for missed SMS, the Menu LED for missed call. Something like that.
That would be cool, I'll await your work and give it a try.
Well, it turns out that works miles better than what i was trying before.
Basically, it now turns the screen on, keeps it locked, flashes the LEDs, turns the screen back off and leaves the home LED on.
Give me about 10 mins and i'll put up a working version. No FC error this time
Can't wait for this!
Sent from my Dell Streak using XDA App
First post updated with a working version
None of the options work on the main screen yet, but they will.
Enjoy
I haven't tried this yet, but I just want to say THANKS! No notification light was driving me crazy! I'm gonna install it now. I like that it would kill the screen but leave the LED light on. That's perfect!
**EDIT**
Well, it didn't work perfectly. Here's what happened on my Beta Streak....
With locking disabled (I use the 'NO LOCK' widget), it turned the screen on and said 'SMS received' and the home LED was on, for about 1-2 minutes, then both went off. When I turned back on the screen and read the msg, the LED went out.
With locking enabled, like most people would be using the app, the screen turned on for a few seconds while the LED pulsed, then both went out. No notification. When I unlock and read the msg, the home LED stays on. I have to 'clear' the app in the notification tray and lock then unlock the screen to make the home LED go out.
Seems like they're little tweaks that could be needed. If you can make this work and be functional, I'll donate to your Paypal! Again, thanks for your work on this project!!
Yeah, it's still pretty much in it's 'Alpha' stage
Cheers, for the feedback, i'll look into the errors.
I know that if the screen is unlocked the Home LED will stay on until you lock/unlock the screen, but that should be an easy fix (hopefully), and i've not set up the Thread's quite right i don't think which could be causing the timing errors.
I'll be spending all of tomorrow getting this thing working so i'll report back
Awesome! You are the man!
A thought for down the road development:
Earlier today when I was thinking about this, I imagined an interface where the user could "record" their own flash sequence for each type of notification they had - email, sms, mms, missed call, etc. Just choose which notification they want to specify, click record, then tap the capacitive buttons in the sequence you want them to light up, then end the recording. Interval timing could be recorded or specified manually. Just a few ideas!
Thanks so much for this. I'll give it a run soon.
Awesome work. Wanted something like this. I hope you will be able to add notifications for misssed calls and gmail as well. Keeping my fingers crossed.
======================================
MiuiFix.zip is mixed from MIUI 2.2.17 & 2.3.2
it can fix Headset(MIUI 2.3.2) or Auto Brightness(MIUI 2.2.17)
MIUI232FIXen.zip does more things:
Fix MiuiSettings
Fix Flashlight (Torch)
Fix Headset
Add 2.3.7 Camera (it can focus)
Add ROOT
Fix wifi (It effects in my phone and I forgot to proint it out yesterday)
If you are using miui 2.2.17
MiuiFix.zip is enough
I believe button leds have a different way of working in miui (working with Auto Brightness)
but if you want the leds work like before (miui 2.2.17、2.3.3 or ealier，just except miui 2.3.2)
you can flash MiuiFix.zip and go into the "use custom" settings once
then flash 2217_signed.zip
you can find 2217_signed.zip in #5
======================================
Timeout.zip adds “Screen Timeout” choices （the red two）
30s 1m 2m 5m 10m 30m Off
but it will lose Korean Language （I hope hpa won't be angry）
I made it from miui 2217
but I believe it can be used in miui 232
for they are nearly the same
======================================
Auto Brightness(MIUI 2.2.17) fixes the crash of the whole phone in custom setting ?
Need to ask...
Can you fix the other issues specifically wifi not working 2.3.2?
• Torch is force closing, but on camera flash is working.
• vibrate doesnt work on messages and pressing home, back, select buttons on phone.
• Also the LED stay on even when the screen is dark.
vanemburghj said:
Can you fix the other issues specifically wifi not working 2.3.2?
• Torch is force closing, but on camera flash is working.
• vibrate doesnt work on messages and pressing home, back, select buttons on phone.
• Also the LED stay on even when the screen is dark.
Click to expand...
Click to collapse
+1
i agree
vanemburghj said:
Can you fix the other issues specifically wifi not working 2.3.2?
• Torch is force closing, but on camera flash is working.
• vibrate doesnt work on messages and pressing home, back, select buttons on phone.
• Also the LED stay on even when the screen is dark.
Click to expand...
Click to collapse
1. Torch in miui 2.2.17 works well in miui 2.3.2
2. In miui 2217 english version (120314)
it works well
3. "settings-display-automatic brightness"
"advanced mode-use custom"
"edit other levels-buttons-0"
or if you want the leds work like before (miui 2.2.17、2.3.3 or ealier，just except miui 2.3.2)
you can （flash MiuiFix.zip and ）go into the "use custom" settings once
then flash 2217_signed.zip
manics said:
1. Torch in miui 2.2.17 works well in miui 2.3.2
2. I have not idea
3. "settings-display-automatic brightness"
"advanced mode-use custom"
"edit other levels-buttons-0"
or if you want the leds work like before (miui 2.2.17、2.3.3 or ealier，just except miui 2.3.2)
you can （flash MiuiFix.zip and ）go into the "use custom" settings once
then flash 2217_signed.zip
Click to expand...
Click to collapse
Thank you for the fixes.
This had managed to fix all my problems, wifi, themes, headset, and leds. Thanks!
Sent from my Dell Streak using xda premium
lordmorphous said:
This had managed to fix all my problems, wifi, themes, headset, and leds. Thanks!
Sent from my Dell Streak using xda premium
Click to expand...
Click to collapse
As for LEDs working, which MIUI version are you using 2.2.17 or 2.3.2? For 2.3.2 had to use advance settings and turn them off completely. Not sure right now if that is an issue or not that will require me to go back to 2.2.17.
vanemburghj said:
As for LEDs working, which MIUI version are you using 2.2.17 or 2.3.2? For 2.3.2 had to use advance settings and turn them off completely. Not sure right now if that is an issue or not that will require me to go back to 2.2.17.
Click to expand...
Click to collapse
Was just about to flash 2.2.17 when I got home since I've been using the Korean version.
MIUI232FIXen fixes the wifi as well for 2.3.2? Because thats the only thing I was waiting on before I flashed it.
tatank_t also posted this notification mod:
http://forum.xda-developers.com/showthread.php?t=1546302
DJ-VAN said:
Was just about to flash 2.2.17 when I got home since I've been using the Korean version.
MIUI232FIXen fixes the wifi as well for 2.3.2? Because thats the only thing I was waiting on before I flashed it.
tatank_t also posted this notification mod:
http://forum.xda-developers.com/showthread.php?t=1546302
Click to expand...
Click to collapse
Yep fixes pretty much everything, install LED patch you recommended works like a charm from my view point. LEDs are off when screen is off and on when screen is on, don't care about blinking when I have some sort of notification. Just wanted them not to always on. Thanks pointing me in the right direction. Did you try 2.3.2 and Manic's patch yet?
everything is works for me, thanks for this fix!
wifi, earphone, gps etc everything perfect!
lordmorphous said:
This had managed to fix all my problems, wifi, themes, headset, and leds. Thanks!
Sent from my Dell Streak using xda premium
Click to expand...
Click to collapse
Confirm flash with MIUI232Fixen.zip is fix wifi issue on MIUI 2.3.2
I will also move to 2.3.2 .....
Screen Timeout is there a fix for less wait time?
Only options I have are 30 seconds, 1 minute than big jump to 5 minutes. Is there patch or fix that will get me to 2minutes?
Applied MIUIFix to 2.2.17, now the LED lights stay on when the screen is off??
Torch works though
mrfr0sty said:
Applied MIUIFix to 2.2.17, now the LED lights stay on when the screen is off??
Torch works though
Click to expand...
Click to collapse
"settings-display-automatic brightness"
"advanced mode-use custom"
"edit other levels-buttons-0"
i think , in miui , button lights have a different way of working
vanemburghj said:
Only options I have are 30 seconds, 1 minute than big jump to 5 minutes. Is there patch or fix that will get me to 2minutes?
Click to expand...
Click to collapse
i have the same demand
I applied this patch and everything seems to be working great on 2.3.2
Thanks manics.
Just curious if anyone here uses any voip or sip apps? I notice Groove IP works great on MIUI- no echo anymore when the person calling me talks. Only issue I have is that the audio sometimes comes through the speaker instead of the earpiece and I have to press the button to switch between the two.
vanemburghj said:
Only options I have are 30 seconds, 1 minute than big jump to 5 minutes. Is there patch or fix that will get me to 2minutes?
Click to expand...
Click to collapse
You desire to achieve
DJ-VAN said:
I applied this patch and everything seems to be working great on 2.3.2
Thanks manics.
Just curious if anyone here uses any voip or sip apps? I notice Groove IP works great on MIUI- no echo anymore when the person calling me talks. Only issue I have is that the audio sometimes comes through the speaker instead of the earpiece and I have to press the button to switch between the two.
Click to expand...
Click to collapse
don't use “Record automatically” in “Call settings”
I am noticing some problems with my s3 after the official jellybean update. It feels like it has been rushed to the phone. For example it doesn't have the quick reply feature in the notification window. It does for missed calls but not for messages. This is one the most anticipated features for me. Also when watching you tube and you don't want the screen to rotate it now does. I want to lock the rotation so I only get the small video at the top when my phone is on its side. It worked before jellybean update. Also auto brightness has changed. When auto brightness is selected you can manually turn it up with the slider in the notification window and it disables auto brightness and changes to what you set on the slider. Now on jellybean you have to uncheck the auto brightness box and then slide. Little features like this are starting to make me feel like it has been a massive rush to get jellybean on to the s3 which is ironic seen as though it took long enough. I have the international i9300 model s3. Is anybody else noticing the problems I have stated? Does anybody know a way of changing/getting the features? Thanks.
They were definitely to busy with the Note II, I mean come on at least give their flag ship the same/some of the features that a bigger version of the S3 has... That sexy multitasking should have been on the initial jelly bean update.
94% to 77 % in 7 hours.
WIFI : On , PSM off
Most power and wakelocks were by Kernal.
Normal?
I'm on LJ4, stock kernel?
I've not got a clue what you're on about?
Sent from my GT-I9300 using xda app-developers app
I know what you mean. The note got great features like the multi window. Apparently that's coming before the new year but I highly doubt that. Are you noticing the same problems I am? Another problem I found is when screen goes off after inactivity you used to be able to press the home button a moment after it goes off and it would turn the screen back on leaving you at the page you was. Now the home button takes you back to the home when you press it. It's annoying you have to go back to the app.
Sent from my GT-I9300 using xda app-developers app
eggman89 said:
94% to 77 % in 7 hours.
WIFI : On , PSM off
Most power and wakelocks were by Kernal.
Normal?
I'm on LJ4, stock kernel?
Click to expand...
Click to collapse
Me too, my problem is the battery with jb lj4
I think there is a few little niggles but overal its pretty much the same.
The autobrightness don't disable automatically now when you adjust the slider as you can now actually adjust the autobrightness brightness, Not sure why though.
Google Now - leaving it active at the mo, but not really found any usefullness from it as yet. The Time home feature is ok, would be good if it actually showed the route I take home - Via motorway, rather than the route through city center which i don't take!!
The new notifcation bar - its ok, nothing major. Expect a bit of all these features will improve over time as well once apps get proper updates. Some work but don't have full functionally - Songpop has no notifications now for example.
Battery Life - I did find that my normal phone use on ISC which included about 50/60 mins worth of calls etc wi-fi left on all the time but only actually connected to wi-fi at home (just 2G & 3G at work) i would have about 55/60% battery life left by the time i got home from work, on Jelly Bean - with the same useage i had about 40/45% left. I am now back to the same as before on ISC, but i didn't disable google now or anything just turned Wi-Fi off when left home and turn it back on when home - results was 55/60% battery remaining a as on ISC. Seems that the Wi-Fi drains when not connected - either it keeps on searching which it might not of done on ISC or its the Google Now doing something (Does say improve location by keeping wifi on - does this even if not connected!!) - Least this way i can still use google now and see how it improves its tags overtime.
I am now using a App called WiFi Timer to automatically switch Wifi on and off when i leave/get home.
Love that it now has voice downloaded so you can text etc with no data connection - find its more accurate now as well!
Never had the small vids on Youtube when rotated phone so not sure about that. Take it disabling autorotate doesn't do this?
Good and Bad
My experience is as follows:
Good:
Sheer speed, no perceivable lag.
A problem I had with only half the SMS notification tone being played (before it cut off) has gone away.
Bad:
Battery drain terrible even when idle. Turning off Google Now, Location Services and Samsung Push Notification fixed this.
When I activate Smart Stay, the screen does not want to turn off 80% of the time - even when I'm not looking at it.
When I wake the phone using the home key, it exits the app I was in. Previously, this would wake the device and return you to the current app (after unlocking). I have a partial work around using the PreHome app; this way the app is still visible underneath the PreHome dialogue box and I just need to press Back to get to my app again.
Widgets, seem to refresh less regularly, particularly Messaging and Gmail widgets which seem to hardly even refresh when I want them too.
Of No Consequence:
The red charging led is a little dimmer when charging.
Overall:
The speed benefits outweigh the niggles - just!
Dan
ohyesman said:
I am now using a App called WiFi Timer to automatically switch Wifi on and off when i leave/get home.
Click to expand...
Click to collapse
No need for an App. You can do it inbuilt.
Go to Wifi, Menu button and Advanced
eggman89 said:
No need for an App. You can do it inbuilt.
Go to Wifi, Menu button and Advanced
Click to expand...
Click to collapse
Yep i know, but this app is far better as it lets you setup different profiles for mornings, evenings & weekends etc which the inbuilt one don't. :good:
root?
i may just root my phone as i really am not happy with this jellybean update, nothing has really improved for me, if i root it and install a rom like codename all the features like quick reply would be there right?
Hi everyone,
I hope this is the right forum, this is my first thread
I am having a problem with ANY AOSP rom I ve installed, no matter wich kernel I try with the rom. When taking a picture with flash in auto mode or ON mode, the phone shuts off and I ve to pull out my battery to reboot. It happens 8/10 times. With flash OFF it works OK
I ve reading lots of threads of people with similar problem even in different devices (nexus, etc). The weird thing is that in tw rom (wanamlite) or any stock sammy rom, the camera and flash works flawless.
I ve tried almost everything. I really want to switch to CM or PA with Halo and this is backing me down.
I ve read in other threads that sometimes is has something to be with the battery but I ve tried 3 different batteries, 2 original and a chinese one, tried taking pictures with battery full, battery low.. and still shutting off on AOSP and flawless on touchwiz.
I ve tried every single camera app in the store. All shutting off my phone in AOSP and working in touchwiz.
however I discovered that with the flash in TORCH MODE (allways on) I can take pictures without any problem. Tasker has an option to take pictures and set the flash to torch and this is what I am using. However, its anoying to use this workaround because with tasker I cannot see what I am taking photo at. And with a camera app that supports torch mode, the flash is allways on, not only when press the take photo button.
I am trying to make tasker turn flash on, press take picture button, and turn flash off, so I can create a scene over the camera app button to make tasker run this task (or use overlays to make a floating widget)
I managed to find the tasker way to press the take photo buton (input keyeven 27), and I tried to use tasker and TESLAflashlight to turn on and off the flash before an after the picture, but teslaled doesnt work while the camera is in use by the camera app.
However, if I use the system widget to toogle flashlight or the flashlight app that comes with CM, the flash on and off switch works while the camera is open!
The problem is that I cannot make tasker interact with the flashlight widget (it is not a shorcut so i cannot use autoshortcut)
Is there a shell command to run in terminal emulator that can turn on/off the flashlight while the camera app is in use? That would solve everything for me..
Any ideas?
Thanks in advance, wonderfull comunity, and sorry for my bad english..
churrolakra said:
Hi everyone,
Click to expand...
Click to collapse
Its not. It needs to go in the Q&A section
churrolakra said:
Hi everyone,
I hope this is the right forum, this is my first thread
I am having a problem with ANY AOSP rom I ve installed, no matter wich kernel I try with the rom. When taking a picture with flash in auto mode or ON mode, the phone shuts off and I ve to pull out my battery to reboot. It happens 8/10 times. With flash OFF it works OK
I ve reading lots of threads of people with similar problem even in different devices (nexus, etc). The weird thing is that in tw rom (wanamlite) or any stock sammy rom, the camera and flash works flawless.
I ve tried almost everything. I really want to switch to CM or PA with Halo and this is backing me down.
I ve read in other threads that sometimes is has something to be with the battery but I ve tried 3 different batteries, 2 original and a chinese one, tried taking pictures with battery full, battery low.. and still shutting off on AOSP and flawless on touchwiz.
I ve tried every single camera app in the store. All shutting off my phone in AOSP and working in touchwiz.
however I discovered that with the flash in TORCH MODE (allways on) I can take pictures without any problem. Tasker has an option to take pictures and set the flash to torch and this is what I am using. However, its anoying to use this workaround because with tasker I cannot see what I am taking photo at. And with a camera app that supports torch mode, the flash is allways on, not only when press the take photo button.
I am trying to make tasker turn flash on, press take picture button, and turn flash off, so I can create a scene over the camera app button to make tasker run this task (or use overlays to make a floating widget)
I managed to find the tasker way to press the take photo buton (input keyeven 27), and I tried to use tasker and TESLAflashlight to turn on and off the flash before an after the picture, but teslaled doesnt work while the camera is in use by the camera app.
However, if I use the system widget to toogle flashlight or the flashlight app that comes with CM, the flash on and off switch works while the camera is open!
The problem is that I cannot make tasker interact with the flashlight widget (it is not a shorcut so i cannot use autoshortcut)
Is there a shell command to run in terminal emulator that can turn on/off the flashlight while the camera app is in use? That would solve everything for me..
Any ideas?
Thanks in advance, wonderfull comunity, and sorry for my bad english..
Click to expand...
Click to collapse
Tried AOSP Camera Mod 2.60 in the themes and apps section?
rootSU said:
Its not. It needs to go in the Q&A section
Tried AOSP Camera Mod 2.60 in the themes and apps section?
Click to expand...
Click to collapse
I am sorry. Didnt realize.. I will post in the correct forum next time.. can I move it to the correct forum or an admin will?
Yes I ve tried that mod, and also tried a port of the tw camera (http://forum.xda-developers.com/showthread.php?t=2370869)
Same problem with both.
Also tried Camera zoom Fx, Camera 360, Pro HDR, Camera JB+, Camera MX, etc... also same problem..
churrolakra said:
I am sorry. Didnt realize.. I will post in the correct forum next time.. can I move it to the correct forum or an admin will?
Yes I ve tried that mod, and also tried a port of the tw camera (http://forum.xda-developers.com/showthread.php?t=2370869)
Same problem with both.
Also tried Camera zoom Fx, Camera 360, Pro HDR, Camera JB+, Camera MX, etc... also same problem..
Click to expand...
Click to collapse
All those camera's that you also tried, just use the existing software and libraries so if your main cam was not working, they definitely wouldn't either.
The TW port isn't fully functional. You'd need to stay with AOSP cameras.
When you say every AOSP ROM you tried, could you name some? It might be a camera firmware issue. There is a thread about camera firmware somewhere.
rootSU said:
All those camera's that you also tried, just use the existing software and libraries so if your main cam was not working, they definitely wouldn't either.
The TW port isn't fully functional. You'd need to stay with AOSP cameras.
When you say every AOSP ROM you tried, could you name some? It might be a camera firmware issue. There is a thread about camera firmware somewhere.
Click to expand...
Click to collapse
I ve tried paranoid android 3.97, cyanogenmod 10.1 , temasek 4.2.2 and temasek 4.3, cdroid, and in each test I tried siyah kernel, googy max, and of course the kernels that comes with that roms by default..
I ve also tried the huawei camera..
I ve updated the camera firmware in the way this threads mentions (http://forum.xda-developers.com/showthread.php?t=2113526)
NOW MY FIRMWARE IS LIKE THIS
Phone/CAM FW Ver Check:
REAR CAMERA:
Cam FW VER: ZDFF03 / (I used to have ZDFE02)
Phone FW Ver: ZDFI02
FRONT CAMERA
CAM&PHONE: S5K6A3
The same problem of phone shutting off used to happened before I updated the firmware..
Really driving me nuts
EDIT:
Now I ve updated the firmware once again and now It is like this
Cam FW VER: ZDFI02
Phone FW Ver: ZDFI02
booted into temasek and the problem persist
:/
Sorry - I do not know the problem then
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Sorry - I do not know the problem then
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Nevermind bro, thank you for your kindness..
UPDATE:
I ve realized that the problem has place only when my battery is below 60%. I am thinking thas the problem has to be with battery/voltage/etc..
The weird thing is that I ve got 3 batteries and in all 3 of them happens the same. And stranger than that, is the fact that on touchwiz I can take pictures with flash even when 5% battery.(so its not a hardware problem)
Maybe AOSP roms have a different way of managing voltages. I ve tried to use steaks and reduce cpu/gpu voltages a little but it didnt help.
I will buy a new battery different to the original ones that i have and try again.
If someone is interested I share my workaround.
I use tasker and use "take picture" using torch mode (I made an scene over the shutter button of the aosp camera app so when I click on it tasker takes the picture). The problem here is that the pictures are stored in tasker folder, so sometimes it takes a while to appear in the gallery.
Or the other method I am using is the following. I used overlays to put a invisible widget toggle of the system flashlight on top left corner of aosp camera, and another invisible widget over the shutter button to trigger a tasker task. The tasker task consist of a couple of console lines that simulates myself touching the screen, so it simulates a touch that toggles de flashlight, then simulates a camera button press and then again simulates a click over the flashlight widget to turn it off.
I know this sucks, but is the only way so far
I ve managed to find a workaround with tasker only
su -c "echo 1 > /sys/class/camera/rear/rear_flash" (turn flash on)
input keyevent 27 (take photo)
su -c "echo 0 > /sys/class/camera/rear/rear_flash" (turn flash off)
The result is pretty the same that the camera flash on.. no blurry pictures, torch duration the same, etc.. so thats it for me..
I hope this can be usefull for people having the same problem.
I tried taking a picture at 30% with "A better camera" with flash and it worked on CM, but with the default camera app the phone goes black
This has been pestering me for quite a while now, at first it started below 20% battery, then 30% and now 50% ... I've ordered a new battery yesterday and I have it charging now, will know when its below 50% when it's any better.
Maybe it has to do with the camera firmware, but I doubt it.
Solved. Was the battery in my case. The 3 batterys. I think that messing around with charging voltaje in stweaks made my batterys gone bad. I ve ordered 3 chinese new batterys and now never shutsoff
Enviado desde mi Galaxy Nexus mediante Tapatalk
Great
Envoyé de mon GT-I9300 en utilisant Tapatalk
Same here, bought a new battery and the problem is solved. Can snap a photo with flash at 2-3% battery left now.
Hey everyone,
This will be a Thread for collecting all the kinds of bugs and other issues you might have encountered.
I talked to the german FB group and talked about them sending them a collection of bugs etc from the community. They gave me an email address (from the communication team) where i can send it to once everything is done.
They will then proceed to send the information to the people developing for axon 7 (A2017G in this case). Of course it's not guaranteed that they will definitely fix all the issues. But it's worth a shot imo.
So at first it's important that bugs have the most importance in this thread since those have to be fixed in order to get an enjoyable oreo experience.
BUT you can also post any features you want to have back (examples are daydream, screen color calibration)
To get things finally started, here are the issues that i gathered so far from this thread:
-SD card mounting issues (SD card doesn't stay mounted after reboot)
-Increased battery drain (mixed opinion, some say it's worse, some say it's the same as nougat)
-Preinstalled apps which are uninstallable (like Accuweather, WPS Office) reinstall themselves after reboot
-Events set in Google calendar don't show a notification
-Bluetooth audio developer options (LDAC, 32bit, 96khz, etc) do not stick
-screencast not working on some miracast devices
-Panorama has lower vertical resolution (approximately 1900px while Nougat had 2800px)
-Charging sound file is missing (now it uses error sound file when connecting/disconnecting USB which sounds really annoying)
Missing Features that you wish to come back or added:
-Screen Color Calibration
-Daydream (which might come back since how they worded it to be temporarily disabled)
-Camera2 api not yet fully implemented
-Vulkan API (was present in Nougat, now removed in Oreo for unknown reason)
-Screen lock app (shortcut in quick settings to lock the device)
-Option to remove Carrier name in status bar
-Dark Mode option (preferably true black background for the while UI like quicksettings menu, settings menu etc for max SOT.)
-More sorting options for stock music player (by title number etc instead of by alphabetical order)
-ZTE Toolbox app
I'm sure there is more. But this is what i have found so far as of now. If there is any more issues you encountered, please post them so i can add them to the list.
Also if i missed any additional info for the issues above, please feel free to tell me.
- Dark mode option
- further dimming option (lowest brightness still too bright)
- screen off toggle/widget
1. Screen cast still won't work well, I never get it connected to miracast since nougat and they didnt fix it on oreo, all my other devices work so good with the same miracast.
2. Battery drain faster than nougat or I think this even worse than oreo beta build B01.
Feature:
- The alphabetical order on music folder for stock music is still annoying. No one hopes listening music from A to Z based on title.
One more:
I don't know if it's just me, but I have a bug where the download manager won't download anything for a long time despite having stable internet connection. This affects Play Store app downloads and downloads other than Chrome (since Chrome has its own download manager it seems). Basically, if I want to quickly download an app or update them, the initialisation starts but it keeps waiting for stuff to download. It won't abort with an error, it just sticks to the spinning circle. In the notification bar you won't see the download arrow animation, which should be there actually. But if I lay down my phone for a while and then pick it up, it may start downloading normally. It's very annoying, you can imagine m
ChiDi9901 said:
One more:
I don't know if it's just me, but I have a bug where the download manager won't download anything for a long time despite having stable internet connection. This affects Play Store app downloads and downloads other than Chrome (since Chrome has its own download manager it seems). Basically, if I want to quickly download an app or update them, the initialisation starts but it keeps waiting for stuff to download. It won't abort with an error, it just sticks to the spinning circle. In the notification bar you won't see the download arrow animation, which should be there actually. But if I lay down my phone for a while and then pick it up, it may start downloading normally. It's very annoying, you can imagine m
Click to expand...
Click to collapse
I know what you mean. But it's not a bug from oreo. I had this too on nougat. Sometimes it still happens. But not as often as it used to be. Dunno what fixes it sadly, but thats probably an issue of play services messing up something since the axon 7 isn't alone. Many other devices have this problem as well sometimes. It comes and goes randomly.
And as you said, chrome and other apps with their own download manager don't seem to have these issues. Again, it's probably play services doing something wrong. Not sure tho, just a guess as play services had many problems in their history
macmobile said:
- Dark mode option
- further dimming option (lowest brightness still too bright)
- screen off toggle/widget
Click to expand...
Click to collapse
What do you mean with dark mode? Like amoled substratum themes? Or like night light?
Poor wifi and 4g reception. This has been my main problem with this rom.
GodOfPsychos said:
What do you mean with dark mode? Like amoled substratum themes? Or like night light?
Click to expand...
Click to collapse
Quick settings, status bar and system settings are all unbearably white. Due to Google's safety measures you can't even use a third party filter anymore.
On Nougat you could change the quick settings to gray at least and use a third party filter for all the rest. On Oreo, no chance at all. What a bad user experience!
So why even bother with a system update, if it doesn't let you adjust the display brightness to your liking anymore?! And I haven't even mentioned the usefulness of an all white UI on an AMOLED screen (Battery!?).
Panorama has lower vertical resolution.
Nougat approx 2800px
Oreo approx 1900px
Signal issues
Hd calls work with incoming but call does not connect for outgoing
Band switching issue band keeps switching thats the main reason for battery drain on 4g
My network is Jio 4g in India
It works in band 3 5 and 40
3 and 5 bands work together but they wont work well with 40 that is they keep switching from one to other with internet connecting and disconnecting
So i switched off band 40 using network signal guru app with magisk root permissions and everything works fine except slow internet speed and persistent hd call issue
Can anyone make solution for band issue
If there is a possiblity to reduce the heat generated during simple tasks.
I had most of those issues: significantly worse battery life, camera freeze when using RAW capture, when I reseted the phone, everything is back to normal, maybe battery is like 5-10% worse than nougat but not sure. Can't say anything about the missing features. I want them too, but most of wanted a Stock + UI and now we complain ? vanilla Android lacks many features like it or not. Hope they release some future firmware update to fix any issues and update the security bulletin.
alexvv said:
I had most of those issues: significantly worse battery life, camera freeze when using RAW capture, when I reseted the phone, everything is back to normal, maybe battery is like 5-10% worse than nougat but not sure. Can't say anything about the missing features. I want them too, but most of wanted a Stock + UI and now we complain ? vanilla Android lacks many features like it or not. Hope they release some future firmware update to fix any issues and update the security bulletin.
Click to expand...
Click to collapse
You had most of these because i used the same thread your post was in as well about the freezing raw capture with stock cam.
But you are the first and only one who had this happen with the camera. So far nobody else reported having the same issue.
alexvv said:
I had most of those issues: significantly worse battery life, camera freeze when using RAW capture, when I reseted the phone, everything is back to normal, maybe battery is like 5-10% worse than nougat but not sure. Can't say anything about the missing features. I want them too, but most of wanted a Stock + UI and now we complain [emoji39] vanilla Android lacks many features like it or not. Hope they release some future firmware update to fix any issues and update the security bulletin.
Click to expand...
Click to collapse
I never ever wanted Stock Android. Stock is the least customizable iteration of Android. So who could want this kind of user experience? People who think Google knows what's best for you? Ridiculous!
Any one tried downgrading to Nougat?
Tried official update.zip. Downgrade FAILS!
This package is for "ailsa_ii" devices; this is a ""
(My device only received official updates, never a custom ROM or root)
Yerry said:
Any one tried downgrading to Nougat?
Tried official update.zip. Downgrade FAILS!
This package is for "ailsa_ii" devices; this is a ""
(My device only received official updates, never a custom ROM or root)
Click to expand...
Click to collapse
You can't downgrade with the official update.zip
Also this is the wrong thread to post this. This thread is for bugs found in oreo.
I appear to be having poor quality sound when playing audio though the main speakers. There's a hissing sound.
GodOfPsychos said:
You can't downgrade with the official update.zip
Also this is the wrong thread to post this. This thread is for bugs found in oreo.
Click to expand...
Click to collapse
I disagree on both of your statements. here is why:
1. It is possible to downgrade, but not with all official update.zip that exist (I succeeded in the meantime!)
2. It is a bug in the Oreo rom that the device type is not set, preventing majority of old update.zip to run since they check the device type
I am missing the stock Nougat 'lock screen' option in the Quick options menu. I am using an app to soft lock the screen at the moment which works but am not sure at all why they removed it in first place.
I am also missing the Messaging and Phone customization options available in Nougat, including the different message bubbles types and the background change settings. It is now simply white and blue and you couldn't change it.
I have had a hard time fixing the Notification problem Oreo brought to many apps, including system, resulting in oversleeping for alarm clock app not working at all. This may not be a particular problem of ZTE directly since apparently it is an Oreo issue but I still don't understand why so many notifications have been forced to the swipe-down menu without default option to disable them. Like "this and this process running in the background" and using default notification tone for every single thing happening to the phone. Adjusting settings in Android System notification modes solved some problems but delayed or not showed at all certain notifications like SMS messages or alarm clock not working - even though these were specifically made to pop and make sound.
Battery life for me varies. It may be up to 10-12 hours if I don't do almost anything and just keep it in stand-by to 3-4-5 hours if I use the screen, some browsing and listening to music. Screen-on-Time in general is up to 2-3 hours in best case scenario. Also sometimes for no apparent reason I see the battery percentage going down like every few seconds by 1 percent and with no use of anything special, just the screen. Overall I could rate it (a little) worse than Nougat considering that I've now gone through all Power settings and disabling anything I don't need per app.
I can only congratulate ZTE for making Dolby Atmos now working on both earphones and front speakers at all times, including with custom player equalizer running at the same time as Dolby Atmos. It never worked for me and was also accompanied with various bugs on all 6, 6.1, 7 and 7.1.
The "choose what your SD card should do" on every restart is pretty bad and I strongly prefer the Nougat behavior when it simply worked. Maybe adding a Setting - "do not ask again" or an option in the System Settings where you can change the status of the SD card on the go would work better than unmounting it every time. This causes many issues with file managers, players and different other apps with files located on the SD card. I hope they re-work it.
Finally, I noticed that Ultra Power Saver works in a much worse way than it did on Nougat. It kind of goes into another OS mode upon return from which it does not start apps that are set to auto-start upon reboot. The Nougat style of simply black-and-whit-ening the screen and turning off any data was so much better and didn't return the phone in a half-functioning state when connected to the charger. Also at 15% as I adjusted it, the middle power saving function (Power Saver or so) does not seem to be at least visibly working so the battery keeps draining as fast as if it was not on.
So, in short - dark(er) Quick Menu, getting back Nougat default app customization options, fixing the SD card message upon every reboot, not forcing TouchPal to be default keyboard or in use even if another keyboard is chosen, or disabling both, and possibly working on better battery life would be all amazing. I still think ZTE did a great job with 8.0 and am happy they finally released it to us.
The phone was frozen and restarted several times.
After that, fingerprint doesn't work and I had to reconfigure fingerprint record.