[ROM] [6.0.1r62][AOSP][CyanideAndroid] [08/19/2016]

plunk

Member
Dec 4, 2009
21
4
0
I rolled back to cyanide because of issues with the dialer app. Don't have time to troubleshoot at the moment.

I can receive and make calls but the second that it dials, the app crashes and the screen is black for the duration of the call. I'm dependent on the other party to hang up. Anybody have ideas on what to try first? I've clean flashed on both twrp and philz and I've tried both tbo gapps from the vrtoxin download site as well as the latest gapps mini set.

Sent from my SCH-I605 using XDA Free mobile app
 
  • Like
Reactions: anthodenn

rgp1236

Senior Member
Nov 5, 2011
84
62
0
Dallas
Thank you!!! I'll be building an update for i605 this evening. Big network improvements

Sent from my GT-N7105 using Tapatalk
Can't wait for the new build!

---------- Post added at 10:20 AM ---------- Previous post was at 10:14 AM ----------

I rolled back to cyanide because of issues with the dialer app. Don't have time to troubleshoot at the moment.

I can receive and make calls but the second that it dials, the app crashes and the screen is black for the duration of the call. I'm dependent on the other party to hang up. Anybody have ideas on what to try first? I've clean flashed on both twrp and philz and I've tried both tbo gapps from the vrtoxin download site as well as the latest

Sent from my SCH-I605 using XDA Free mobile app
I have the same issue. I hit the power button to put it to sleep, then again to wake and the home button. I can then bring up the call and hang up. I don't make that many calls so it is not an issue for me. ... I have now found after some testing that the method is not consistent. Will continue to investigate.
 
Last edited:

rogersb11

Senior Member
Nov 18, 2013
3,345
6,888
0
Indianapolis
Can't wait for the new build!

---------- Post added at 10:20 AM ---------- Previous post was at 10:14 AM ----------


I have the same issue. I hit the power button to put it to sleep, then again to wake and the home button. I can then bring up the call and hang up. I don't make that many calls so it is not an issue for me. ... I have now found after some testing that the method is not consistent. Will continue to investigate.
If your guys' screen is going black it's a proximity sensor issue. Phone app behaves perfectly for me and has for all version of VRT. You will have to manually turn the screen off during calls if using the option I'm about to mention but that's better than going totally dark. In Dialer settings you can turn off the proximity sensor so that YOU control screen on and off and the sensor is totally disabled. About the build, I found some underlying issues with clock/greeting/ticker(I just brought ticker back from the dead this week as google removed it from MM). I'm watching football today but have started totally rewriting all that code that controls visibility with these three things and when I get it fixed up I will build for i605, guessing will be today but by tomorrow it will be done for sure. Sorry for the delay but you guys know how I am about releasing something I'm not happy with, it basically doesn't happen lol
 

rgp1236

Senior Member
Nov 5, 2011
84
62
0
Dallas
You are absolutely correct! It is the proximity sensor, but it can be disabled from the phone call settings. Tap the phone icon, then the 3 dots on the upper right. Choose settings, then Calls. Turn off enable proximity sensor. Issue resolved.
 

rgp1236

Senior Member
Nov 5, 2011
84
62
0
Dallas
If your guys' screen is going black it's a proximity sensor issue. Phone app behaves perfectly for me and has for all version of VRT. You will have to manually turn the screen off during calls if using the option I'm about to mention but that's better than going totally dark. In Dialer settings you can turn off the proximity sensor so that YOU control screen on and off and the sensor is totally disabled. About the build, I found some underlying issues with clock/greeting/ticker(I just brought ticker back from the dead this week as google removed it from MM). I'm watching football today but have started totally rewriting all that code that controls visibility with these three things and when I get it fixed up I will build for i605, guessing will be today but by tomorrow it will be done for sure. Sorry for the delay but you guys know how I am about releasing something I'm not happy with, it basically doesn't happen lol
Just realized we are talking about the same settings. I read dialer settiings as the system menus. Oops.
 

2pezboy

Senior Member
Jun 22, 2011
68
20
0
Disabling proximity sensor isn't a big deal for me. I am super impressed with this being the first build!

Did full wipe of everything (including SD card) and clean install (w/TBO). Biggest issue I am having is inability to paste anywhere and can't copy in some places. Someone in the AT&T thread mentioned the same. Tried dirty flashing and didn't help. I noticed copy/paste pop-up is at the top of the display and not floating like I saw on MM reviews. Should it be?

In cyanide, there used to be an option to not have to click enter after entering 4 digit unlock pin. (automatically unlocks after 4th digit is entered). Is that option not in Toxin build or am I just not finding it?

Thanks, Brett, for your amazing work! Small donation coming at ya. I appreciate your time and efforts!!!

---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------

And don't apologize for any delays, Brett!! Well worth the wait!

---------- Post added at 10:55 PM ---------- Previous post was at 10:02 PM ----------

I just remembered I have also seen some occasional excessive battery drain. Not sure where it's coming from. Screen is hot when it happens. Battery stats says Android OS is by far highest consumer of battery. On all other OS versions Screen has always been highest. I haven't seen screen come anywhere close on MM yet.
 

DrunkUncas

Senior Member
Aug 14, 2008
666
189
43
First full day- horrific battery life. Got 12 hours of light use. Same drain as reported above.

I also had a paste issue.

My calls are fine, but I just replaced my proximity sensor. At this age, you guys should probably do the same the next time you have it apart.

Don't apologize for any delays. There's only about a dozen of us still on this phone. We can wait.

ETA: Looks like I'm unable to receive calls. Rings, but screen doesn't light up- even when buttons are pressed.

Wifi tether turns on, but isn't detected by my computer.
 
Last edited:
  • Like
Reactions: 2pezboy

rgp1236

Senior Member
Nov 5, 2011
84
62
0
Dallas
If your guys' screen is going black it's a proximity sensor issue. Phone app behaves perfectly for me and has for all version of VRT. You will have to manually turn the screen off during calls if using the option I'm about to mention but that's better than going totally dark. In Dialer settings you can turn off the proximity sensor so that YOU control screen on and off and the sensor is totally disabled. About the build, I found some underlying issues with clock/greeting/ticker(I just brought ticker back from the dead this week as google removed it from MM). I'm watching football today but have started totally rewriting all that code that controls visibility with these three things and when I get it fixed up I will build for i605, guessing will be today but by tomorrow it will be done for sure. Sorry for the delay but you guys know how I am about releasing something I'm not happy with, it basically doesn't happen lol
Thanks for the update. Already running and testing!
 

2pezboy

Senior Member
Jun 22, 2011
68
20
0
I am seeing the same with WiFi tethering seeming to turn on fine, but none of my devices can see it as even available.

---------- Post added at 11:03 PM ---------- Previous post was at 10:57 PM ----------

Just saw an update posted yesterday (1/17). Checking it out now. Thanks, Brett!!

---------- Post added at 11:49 PM ---------- Previous post was at 11:03 PM ----------

I am seeing the same with WiFi tethering seeming to turn on fine, but none of my devices can see it as even available.

---------- Post added at 11:03 PM ---------- Previous post was at 10:57 PM ----------

Just saw an update posted yesterday (1/17). Checking it out now. Thanks, Brett!!
Copy /paste working for me on 1/17 build! (dirty flashed over 1/11 build)

Will keep an eye on battery drain and check out tether tomorrow.

Thanks, Brett!
 
  • Like
Reactions: rogersb11

xflbret

Senior Member
Mar 15, 2013
316
28
28
Tucson, AZ
I am still on the Note 2. I haven't installed this build yet, but I wanted to drop a note to thank the dev for working on it still. With the inability to unlock bootloaders for the newer phones, or even root some of them, I am legitimately not understanding why many more people haven't stuck with the Note 2 as I have. Thank you to the few of you remaining who keep working on this phone.
 

mschiska

Member
Jun 9, 2013
11
1
0
I just installed this last night and I love it. Thanks to Brett for another fine rom! Everything working great! Only issue I have is I get little lines in video playback. I don't think it's rom specific but rather aosp issue. Happens with CM and CyanideL as well. I've been looking around for a fix. I always do clean install and follow directions from OP exactly!