[Q] Device Encryption 4.2.x / 4.3.x - Sprint Samsung Galaxy Note II

Is anyone else experiencing broken device encryption? I theorize its related to the enforcing/permissive issue. I struggle to get my modem to stay, & at times it shows my other lines info! To attempt a resolve I have flashed several kernels from 4.4.2 l900 roms like carbon, cm, pa on cm base, If baseband is still breaking I go back to LJC for a fix then jump to 4.3. And encryption remains busted on TW or CM.

Related

[Q] Audio Stopped Working

Hey guys,
I'm sorry if this has been posted before, but I've searched on the forums and on Google with no luck. Recently, my sound stopped working on my GSIII running CarbonRom 1.6. Nothing out of the ordinary happened, it just stopped working one day. Also when I'm in a call, the person on the other line cannot hear me. I've checked the sound settings numerous times and have made sure that I am not in silent mode.
I have tried other 4.2.2 ROMs and they all have produced the same result. I have also tried a factory reset and formatted data in TWRP. I reverted back to stock and have noticed that the sound seems to work when I'm not running 4.2.2 ROMs. Does anyone know what the problem might be? I really prefer the look and feel of vanilla Android and I'm really bummed out that 4.2.2 ROMs seem to kill sound. Thanks.
re: 4.2.2 roms
jdsung said:
Hey guys,
I'm sorry if this has been posted before, but I've searched on the forums and on Google with no luck. Recently, my sound stopped working on my GSIII running CarbonRom 1.6. Nothing out of the ordinary happened, it just stopped working one day. Also when I'm in a call, the person on the other line cannot hear me. I've checked the sound settings numerous times and have made sure that I am not in silent mode.
I have tried other 4.2.2 ROMs and they all have produced the same result. I have also tried a factory reset and formatted data in TWRP. I reverted back to stock and have noticed that the sound seems to work when I'm not running 4.2.2 ROMs. Does anyone know what the problem might be? I really prefer the look and feel of vanilla Android and I'm really bummed out that 4.2.2 ROMs seem to kill sound. Thanks.
Click to expand...
Click to collapse
That's an easy questiion, like I have been saying all along none of the cm10/aosp/aokp or ported roms
are ready for prime time, they are good for those who want to experiment with a few features not found
in stock t999 4.1.1 Touchwiz Jellybean roms. None of the cm/aosp/aokp roms even have the Wifi calling feature.
That's why after trying all the aosp/aokp/CM and ported roms I have come to the conclusion above.
So unless you like experimentation only flash T-Mobile T999 stock 4.1.1 Touchwiz Jellybean roms
or any of the custom roms which are based on T-Mobile T999 Touchwiz v4.1.1 Jellybean stock rom.
The best custom T999 T-Mobile Touchwiz Jellybean 4.1.1 based rom in my opinion
is the Wicked v9.1 custom rom, check it out you won't be disappointed.
Good Luck!
You could always try to flash your 4.2.2 Tim of choose and choose not to restore Google backup, Google backs up settings. If it works without setting up your account then go from there.
Sent from my SGH-T999 using xda app-developers app

TMO T999L questions

Hello I have a couple questions about my T999L I am running a stock deodexed rom but the baseband and the build #s don't match baseband is MK4 and build MK7 is this a problem ? Also I am on version 4.1.2 I would like to get up to a custom 4.3 Rom what ones can I use? I had to come back to this because my wifi wouldn't work? thank for any help.
Its quiet possible that you had different Modem than your Rom. No issues. It sounds like you got this phone from someone else. They may not have flashed insecure kernel. That's the reason for Wi-Fi Not Working.
So long you don't have signal issues, its fine to keep that modem. As to 4.3 Roms, there's plenty to choose from.

Can't Toggle LTE on Cyanogenmod 11

It's stuck on off and I'm afraid of being stuck on 3G permanently.
Singin' Bluebird said:
It's stuck on off and I'm afraid of being stuck on 3G permanently.
Click to expand...
Click to collapse
Exactly my issue as well, verizon galaxy s4, any ideas on how to get 4G/LTE working?
pandora808 said:
Exactly my issue as well, verizon galaxy s4, any ideas on how to get 4G/LTE working?
Click to expand...
Click to collapse
I'm on Galaxy SIII from Sprint. I was running latest Beanstalk and same issue happened to me and others once flashing the 4.4.2.249 build if I remember right, and we lost LTE ability, 3G worked. It looks like the problem was related to the Cyanogenmod 11 source code which Beanstalk is based on.
In order to fix it, we had to revert back to a stock rooted 4.3 rom, wait until had LTE back (which was few minutes for me), and then back to a previously working Beanstalk Rom. I tried to recover from my backup before going to rooted 4.3 rom but that did not bring back my LTE so that's why I went back to 4.3 rooted first and then after getting LTE on that I recovered from my previous backup.
Seems other roms based on the same source are all having same issue. I'm waiting for someone to confirm that LTE works before doing any other Rom flashes. I love the Beanstalk Rom by the way and the amazing work of Cyanogenmod team.
KillerPie said:
I'm on Galaxy SIII from Sprint. I was running latest Beanstalk and same issue happened to me and others once flashing the 4.4.2.249 build if I remember right, and we lost LTE ability, 3G worked. It looks like the problem was related to the Cyanogenmod 11 source code which Beanstalk is based on.
In order to fix it, we had to revert back to a stock rooted 4.3 rom, wait until had LTE back (which was few minutes for me), and then back to a previously working Beanstalk Rom. I tried to recover from my backup before going to rooted 4.3 rom but that did not bring back my LTE so that's why I went back to 4.3 rooted first and then after getting LTE on that I recovered from my previous backup.
Seems other roms based on the same source are all having same issue. I'm waiting for someone to confirm that LTE works before doing any other Rom flashes. I love the Beanstalk Rom by the way and the amazing work of Cyanogenmod team.
Click to expand...
Click to collapse
Works on AOSB, Updating PRL and profile in between flashes can help.

[Q] Paranoid Android 4.5 beta 3 unfixable lingering calling bug

Hello everyone,
I'm posting on here because I can't find any solution to my dilemma which I am sure that other people in the AOSPA legacy community have also experienced. I have been using Paranoid Android on my T989 since the 4.4.3 update and I have regularly updated my roms since then. Somehow ever since I updated my phone to 4.5 beta 3, something prevents me from being able to hear or be heard during regular phone calls around an hour after I restart my phone.
I have tried everything to try to make my phone back to normal, I have updated my versions of AOSPA, I have downgraded to stable versions, I have gone to a debloated stock rom (which worked perfectly fine but who likes touchwiz android 4.1.2?) and back to AOSPA, I tried the latest Carbon nightly rom and the problem persisted, I have wiped my internal memory, cache, davlik, etc. multiple times. I am at a total loss as to what I should do to fix this issue. I'm currently running it on 4.6 beta 1 and I still have the issue.
I really love my GS2 and I don't want to part with it or have it running stock. Please help me.
I really appreciate it,
Chris
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Playnhooky said:
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Click to expand...
Click to collapse
I am also getting this problem on Slim 7.8....must be an audio-caf issue....Can someone go back to an old KK rom (one from earlier months) and see if they experience the same issue? Preferably cyanogenmod
I flashed to stock rom via oden and spent the weekend with the phone and all was good , I flashed to the latest cm-11 with no addons , stock cm-11 kernal and after an hour or so I lost call audio again . We must have done something to the phone in a previous rom cause not many people are having this issue . Now I have flashed about 75 different roms with no issue , I hope someone finds the problem cause I'm not to keen on the stock rom !
I've seen posted that snapchat was the cause of the no call audio problem we are having , I flashed the latest liquid smooth rom last night , download all my apps that I usually do except snapchat and I've had no issues with the calling bug . All is working great .

[FIX] GPS issues on ASOP based ROMS

If you are having issues with GPS on AOSP based ROMS all you need to do is:
*flash a stock ROM (stock ROM is one based on the LG ROM that came with the phone I recommend this one http://forum.xda-developers.com/verizon-lg-g3/development/rom-stock-root-deodex-t2932683 )
*get a gps lock
*then flash or restore whatever AOSP based ROM you like.
GPS will now be working for you.
This has been a fix for GPS on AOSP based roms for years and I had to recently use it myself as I was getting no GPS on all AOSP based ROMS.
Also make sure that GPS isn't actually broken in the AOSP based ROM you are flashing because if GPS is broken in the ROM then obviously this isn't going to fix it. This fix is for people having GPS issues on ROMs that have working GPS which is currently all KK and LP AOSP based ROMs we have for the vs985. Hope this helps someone.
bump. Still seeing people posting about no gps on AOSP roms so bumping this in hopes that it gets seen more often.
Interesting. Just curious here: If I "Restore" a 4.4.4 ROM, get the lock, then Restore back my current AOSP Lollipop-based ROM, will that work? As in, is the GPS lock sequence stored in the GPS hardware flash or something?
joeinbend said:
Interesting. Just curious here: If I "Restore" a 4.4.4 ROM, get the lock, then Restore back my current AOSP Lollipop-based ROM, will that work? As in, is the GPS lock sequence stored in the GPS hardware flash or something?
Click to expand...
Click to collapse
Honestly I don't know why this fixes GPS I just know it does. Like I said in the OP this has been a fix for GPS on AOSP based ROMS for years as I learned this trick back a couple years ago on my LG Spectrum. I was one not getting GPS on any AOSP based roms but noticed most weren't having issues with it so I remembered this fix and tried it on my phone and I haven't had GPS issues since. Once you do this you should no longer need to again no matter how many roms you flash; just be sure to always get a lock on each ROM you flash before flashing a new one as that may cause the issue to comeback.
Bumping again because people are still constantly posting about gps being broken on AOSP based ROMS and don't know how to research the forums for solutions to their issues but would rather clutter threads with the same questions over and over and over.
Help
So does "get a gps lock just mean open up maps and get it to lock onto a gps signal?

Categories

Resources