Related
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
flashroyal said:
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
Click to expand...
Click to collapse
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
stefan2012 said:
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
Click to expand...
Click to collapse
Logs?
JoinTheRealms said:
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Click to expand...
Click to collapse
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
flashroyal said:
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
Click to expand...
Click to collapse
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
JoinTheRealms said:
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
Click to expand...
Click to collapse
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
flashroyal said:
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
Click to expand...
Click to collapse
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
JoinTheRealms said:
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
Click to expand...
Click to collapse
I don't know why, but every time I tried to record screen, phone just reboots. I tried with various apps, every time same thing. I cant find built in app in beanstalk 4.4. I'll try stock again but cant before tomorow. Thank you for your time
Use beanstalk with grouper blobs, and press vol up and power simultaneously to record
Sent from my LG-P880 using Tapatalk 4
I just got my droid turbo about a week ago, and I've since Been hearing about all the battery drainage issues and charging issues, all of the apps I use are compatible with 4.4 KitKat, so I'm a little leery of upgrading because I use my phone a ton and the massive battery was the main reason I got it over an S6, and so if that is negated, is there any reason to upgrade?
Jordaneer said:
I just got my droid turbo about a week ago, and I've since Been hearing about all the battery drainage issues and charging issues, all of the apps I use are compatible with 4.4 KitKat, so I'm a little leery of upgrading because I use my phone a ton and the massive battery was the main reason I got it over an S6, and so if that is negated, is there any reason to upgrade?
Click to expand...
Click to collapse
My Turbo never had any of the issues others had. Easily get over a day with moderate to heavy use; 2 days with light usage. I'm still on 4.4.4. If you're worried about it, head over to the development section and follow the steps to flash 5.1 without eliminating your option to go back to KitKat.
As is all too common in these forums, those who experience problems go out of their way to publish them, giving the impression that everyone has issues when most, like I, experience none of them. If you are comfortable with the rather detailed (but manageable) process for getting rooted and reversible 5.1, then by all means go that route.
Otherwise, if you are happy with KitKat, don't feel pressured to go to Lollipop. On the other hand, most users (but by no means ever all users) that have taken the OTA upgrade are just fine with the results, with comparable battery life and improved performance in some functions.
Most users have reported that wiping cache solves their performance and battery issues. In your case, I would recommend a full wipe after the upgrade, ask around and you'll find that full wipe after update has almost 99.9% success rate.
So today was my first day being on rooted 5.1.
I unplugged at about 11am, and am now hitting 10% battery 9 hours later. That should suck right?
Well I also wanted to drain my battery today so I just let my phone stream video (plex library ftw) at max brightness.. 8 hours of straight screen on time...
I think in a normal usage day (where Im not trying to kill the battery) I clock 2-3 hours of on screen time...
So if we extrapolate that out, I'm just guessing... I would've made it 20-30 hours of battery at my normal usage.
Is that good? Dunno. No worse than when I was on rooted KK.. perhaps, I think, even better?
I also dirty flashed 5.1 over my 4.4.4.. never wiped cache or FDR.
Hearing that, its up to you to decide what to do, for me I'm sticking with rooted 5.1 and couldn't be happier.
I didn't know you could root 5.1 on droid turbo
Kiwironic said:
I didn't know you could root 5.1 on droid turbo
Click to expand...
Click to collapse
The breakthrough came from this thread yesterday: FrankenPop
Which then lead to this thread late last night: Instructions and first released image
Computerfreek released his image early this morning: Thread
Working from home has its benefits.
EDIT: I am surprised Droid-life or no other outlet has really picked up on this yet.
Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.
Kiwironic said:
Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.
Click to expand...
Click to collapse
You can't root from the ota so do not update that way!!!!
Kiwironic said:
Well, if you can root 5.1, then there's are no cons to upgrading really. You can have customisation as well as the new user experience.
Click to expand...
Click to collapse
Well if you go to the threads you'll see the root method requires 4..4.4 boatloader.. so taking the official update overwrites the bootloader to 5.1 and at that point there is no going back.
So for the average user, taking the upgrade is a major deal.. for those that don't mind some adb/fastboot work.. absolutely, go back and forth from KK to LP everyday! Just dont touch that 4.4.4 bootloader.
Thanks for the update. It makes sense now. We not talking upgrade vs staying on 4.4.4 we are talking upgrade path.
I see, I am still looking forward to finding a way to upgrade my xt1225 to 5.1 without data wipe, but so far there is nothing for us, no OTA or images yet. No upgrade path in sight
No. You would going from best to OK.
I upgraded to 5.1 and for me it was a mistake. My most valuable app (Record My Call) doesn't work with 5.1 and no other similar app will work either. I'm going to buy another another Droid Turbo on KitKat and sell my 5.1.
Ken
I updated both my and my wife's DT via the OTA. We didn't have root before and I simply haven't needed it, so I figured I'd just go ahead (if anything went wrong, I would have to harass Verizon, but so be it). In the end, both phones are working well (knock on wood)... and I didn't do the cache or factory reset either. Battery life is fine, even with some gaming... so it might be better than KK was, but it's certainly not worse for me.
emgo said:
I upgraded to 5.1 and for me it was a mistake. My most valuable app (Record My Call) doesn't work with 5.1 and no other similar app will work either. I'm going to buy another another Droid Turbo on KitKat and sell my 5.1.
Click to expand...
Click to collapse
Google Voice does this without needing an app.... that might get you a solution for free?
Seems like there are plenty of updated apps that can work in LP as well: https://www.androidpit.com/forum/632761/best-call-recorder-app-for-android-5-lollipop
schwinn8 said:
I updated both my and my wife's DT via the OTA. We didn't have root before and I simply haven't needed it, so I figured I'd just go ahead (if anything went wrong, I would have to harass Verizon, but so be it). In the end, both phones are working well (knock on wood)... and I didn't do the cache or factory reset either. Battery life is fine, even with some gaming... so it might be better than KK was, but it's certainly not worse for me.
Google Voice does this without needing an app.... that might get you a solution for free?
Seems like there are plenty of updated apps that can work in LP as well: https://www.androidpit.com/forum/632761/best-call-recorder-app-for-android-5-lollipop
Click to expand...
Click to collapse
This is from google Voice help.
"It's not currently possible to record outbound calls made through your Google number at this time."
Tried many recommend apps, none work. Found this information in a couple of places.
https://bitbucket.org/copluk/acr/issues/257/after-upgrading-to-android-5-cannot-record
"Motorola has stopped 2 way call recording support with Android 5. This is not our fault. Try any other call recording app you'll see that none works.
Your only option is to set audio source to MIC and set loudspeaker on.
I hope you understand and increase your star rating"
I'm currently looking for a used Turbo still on KitKat
Thanks,
Ken
emgo said:
This is from google Voice help.
"It's not currently possible to record outbound calls made through your Google number at this time."
Click to expand...
Click to collapse
Thanks for the info on Google voice not supporting outgoing calls. I didn't need it, so I never tested it.
emgo said:
Tried many recommend apps, none work.
Click to expand...
Click to collapse
I did a quick search and the recommended app was BoldBeast Recorder. I just tried it with a standard voice call (not GV) I had with my wife (outgoing if it matters) and it worked just fine in Mode 1. After the install, it defaulted to Mode 4 and didn't work, so i was going to start with Mode 1 and go from there... but it just worked there, so i didn't have to go further. To recap, I'm on the OTA updated Lollipop... no factory reset and no cache wipe.
schwinn8 said:
Thanks for the info on Google voice not supporting outgoing calls. I didn't need it, so I never tested it.
I did a quick search and the recommended app was BoldBeast Recorder. I just tried it with a standard voice call (not GV) I had with my wife (outgoing if it matters) and it worked just fine in Mode 1. After the install, it defaulted to Mode 4 and didn't work, so i was going to start with Mode 1 and go from there... but it just worked there, so i didn't have to go further. To recap, I'm on the OTA updated Lollipop... no factory reset and no cache wipe.
Click to expand...
Click to collapse
In mode 1 it records the call but like every app I've tried after the update to Lollipop it's using the microphone to record the call. My voice is loud and clear but the other person's voice is very faint or not heard at all. Did you get different results? Before the update "Record My Call" worked perfectly, it recorded the actually conversation somehow without using the mic.
Thanks,
Ken
emgo said:
In mode 1 it records the call but like every app I've tried after the update to Lollipop it's using the microphone to record the call. My voice is loud and clear but the other person's voice is very faint or not heard at all. Did you get different results? Before the update "Record My Call" worked perfectly, it recorded the actually conversation somehow without using the mic.
Thanks,
Ken
Click to expand...
Click to collapse
I did find my voice was a little louder, but my wife's was perfectly audible. Both required me to turn the volume up, but they worked fine and both were clear...
Maybe another mode would work better, but this was fine for my limited usage.
So I read these complaints and have decided to opt out of the upgrade to Lollipop on my Droid Turbo. When the upgrade notification screen came up, I just put no, and I haven't gotten a notification since. It's been a few weeks for me. A few other people in my family have the same phone. Unfortunately when they click "no" they seems to get the upgrade prompt again a few days later. I'm not sure why the prompt hasn't come up for me again.
Is there a way to stop the upgrade notification prompt for showing up repeatedly without root? I know that there are apps on a rooted system that can prevent the notification. I'm hoping there's a way to prevent it without root. Thanks for any info!
schwinn8 said:
I did find my voice was a little louder, but my wife's was perfectly audible. Both required me to turn the volume up, but they worked fine and both were clear...
Maybe another mode would work better, but this was fine for my limited usage.
Click to expand...
Click to collapse
I tried all modes and mode 1 seems best. I tried many apps that use the microphone and they are all about the same. They work OK if you are in a quite area but a noisy environment or step outside when the wind is blowing and the microphone recorders don't work well at all, not for me. I'm watching Ebay and Craigslist for one still on Lollipop. 64GB models are bringing around $400 no matter which OS they are on. Mine should bring about the same amount that I pay for one with KitKat so hopefully it won't cost much to correct my mistake of upgrading.
Ken
Very tempted to update to Android N (Team FXP AOSP)
But I value my camera quality (Using DRM fix kernel, works great)
Knowing that the Xperia is never going to get android N, due to google removing the Z3's kernel from their source, would it be worth updating to AOSP, basically removing all the features that are so good?
You answered your own question, stick to stock if you want a camera that works 100% well. AOSP camera has never been good for any phone and the camera on Nougat barely works anyway.
Next best thing is Concept ROM, which still has a decent camera
I'm tempted to try Nougat AOSP. I don't mind losing the camera on Z3c that much since I prefer my camera on my G4. But I don't know how to install it. Is there a guide? That's up? Last time I checked Sony's site the guide was down.
Two qustions, how bad does the camera become, is it still usable for simple random snaps to send to friends on IMs?
What is DRM fix kernel?
TIA
Lol nougat barely works. I've been running it for days now. My opinion is nougat is excellent on z3c. I can upload a flash able zip with full Google apps if people are interested
mcgi5sr2 said:
Lol nougat barely works. I've been running it for days now. My opinion is nougat is excellent on z3c. I can upload a flash able zip with full Google apps if people are interested
Click to expand...
Click to collapse
If that was a reply to me, I was referring to the camera
tomascus said:
If that was a reply to me, I was referring to the camera
Click to expand...
Click to collapse
sorry pal.
camera isn't really use-able yet
everything else worked great
mcgi5sr2 said:
sorry pal.
camera isn't really use-able yet
everything else worked great
Click to expand...
Click to collapse
Which android security patch is it on?
Battery life good?
BrotherZero said:
Which android security patch is it on?
Battery life good?
Click to expand...
Click to collapse
I get a solid two days, and as a CoC player thats pretty dam good
mcgi5sr2 said:
I get a solid two days, and as a CoC player thats pretty dam good
Click to expand...
Click to collapse
That does sound good. Get 6-8h SOT with SLiMM ROM. Do you know how much you get on this one?
Also could you do me a favour and check which Android Security Patch it got? It would be awesome if PA is up to date with that.
TIA
BrotherZero said:
That does sound good. Get 6-8h SOT with SLiMM ROM. Do you know how much you get on this one?
Also could you do me a favour and check which Android Security Patch it got? It would be awesome if PA is up to date with that.
TIA
Click to expand...
Click to collapse
Security patch is September. Its built off the main branch of AOSP google sources. So security will always be uptodate
mcgi5sr2 said:
Security patch is September. Its built off the main branch of AOSP google sources. So security will always be uptodate
Click to expand...
Click to collapse
Thanks, mate! might give this a try then. Shame abut the camera, but I guess ill found out how unusable is. Hopefully there is a fix soon.
Sony fix the AOSP camera if they wanted to?
Enviado de meu D5833 usando Tapatalk
mcgi5sr2 said:
Security patch is September. Its built off the main branch of AOSP google sources. So security will always be uptodate
Click to expand...
Click to collapse
Please could provide a link to the Rom Nougat 7.0
Can you please share the gapps, or tell me which ones you are using? I got cm gapps or open gapps from cm website (for 7.0) and my google play services keep crashing.
Thanks,
mcgi5sr2 said:
Lol nougat barely works. I've been running it for days now. My opinion is nougat is excellent on z3c. I can upload a flash able zip with full Google apps if people are interested
Click to expand...
Click to collapse
https://www.androidfilehost.com/user/?w=settings-dev-files&flid=73595
Is where I am posting all the builds I put together. So be warned that if it doesn't boot it was just a test version. AFAIK the latest ROM should boot fine without issue. GApps are already installed on all the flashable zip versions in that location
mcgi5sr2 said:
https://www.androidfilehost.com/user/?w=settings-dev-files&flid=73595
Is where I am posting all the builds I put together. So be warned that if it doesn't boot it was just a test version. AFAIK the latest ROM should boot fine without issue. GApps are already installed on all the flashable zip versions in that location
Click to expand...
Click to collapse
Hey thanks. Quick question, you said you have been running nougat on your device and everything (but the camera) seems to be working. I just installed it last night (and my gapps are working as well now) and I already noticed a couple of bugs. First and most important, i can't hear the person on the other end of the line. It appears that my earpiece is not working. The person on the other end can hear me, but I can't hear that person. Second and minor issue, once i plug in my z3c to charge, the battery icon top right shows the charging sign as it should. However when i unplug, that charging sign doesn't go away. So far i have noticed these bugs, can you confirm if you are not facing these bugs (so I know its my device that is messed up).
Thanks,
flintfirewalker said:
Hey thanks. Quick question, you said you have been running nougat on your device and everything (but the camera) seems to be working. I just installed it last night (and my gapps are working as well now) and I already noticed a couple of bugs. First and most important, i can't hear the person on the other end of the line. It appears that my earpiece is not working. The person on the other end can hear me, but I can't hear that person. Second and minor issue, once i plug in my z3c to charge, the battery icon top right shows the charging sign as it should. However when i unplug, that charging sign doesn't go away. So far i have noticed these bugs, can you confirm if you are not facing these bugs (so I know its my device that is messed up).
Thanks,
Click to expand...
Click to collapse
Hi!
I'm using the latest AOSP for our devices, and facing thiese bugs too. ( 20160912 ). Sometimes I've got calling bug when I can't hear the other person on the line, but he can hear me. Just a restart solves it, but I've got thiese problem nearly evry tenth call time... And one more thing, while i'm on calling and my phone set to minimum volumes, everyone else could to hear my phones speak... or I can say it, what you're talking about. Like when i set the speak to a loudspeaker, as though it were the whole conversation. The speakers are very loud on minimum volume, and not too much louder on maximum settings. ( but, i think they are a known bug ).
Second, the cahrging icon. Yes I experienced it too, when you disconnect the charger from the phone, the icon remain the same, like when the charger plugged in.. And I think, something gping on the background, because my battery goes down nearly 30 percent by a night ( 8h ).
About the rom speed. I think, it runs very smooth / fine until more than five software parallel, ROM while fast. If more than five program run in the background, ROM start to tear, slow down. If you delete them from the memory, the system will be fast again.
I tried to take a logcat with "aLogcat" from playstore, but it's not working. I remember it from my previously phone age, i must convert it to system app... But now, I can't do this, because i did it with Titanium Backup, and now they not support andoid N..
Anyway, I think its will be a very good AOSP rom... ( without camera :/ )
Having a small issue with call quality, had it on every version of OOS yet. People I call or who call me complain that either a) my voice quality is not great, or b) they can hear an echo of themselves for the first 30-60 seconds or so, then it goes away. This is on AT&T in the US. Anyone else seeing anything like this, or is it likely a hardware problem I should contact OP about?
It seems to be pretty common. There is a file called Echofix.zip that fixes it but I don't know if it works on OOS. I only used it on RR rom.
bird333 said:
It seems to be pretty common. There is a file called Echofix.zip that fixes it but I don't know if it works on OOS. I only used it on RR rom.
Click to expand...
Click to collapse
Do you have file or url by any chance.. have been trying to find it
bird333 said:
It seems to be pretty common. There is a file called Echofix.zip that fixes it but I don't know if it works on OOS. I only used it on RR rom.
Click to expand...
Click to collapse
I am completely stock right now, can it be flashed through stock recovery?
ram4ufriends said:
Do you have file or url by any chance.. have been trying to find it
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70097082&postcount=96
Again I don't know if this will work for a stock rom. If you try it report back.
TXRangerXDA said:
I am completely stock right now, can it be flashed through stock recovery?
Click to expand...
Click to collapse
did you try to flash the zip file on stock ROM? is it working?
Honestly don't remember. I ended up sending it back to OP, they sent it back saying they couldn't reproduce the issue. A month later I sent it back again, because it was really unusable for me. No one could hear me on most calls. Voip worked fine. They still couldn't reproduce it, but refunded the cost of the phone to me. Bought a Samsung s8+ a few months later.