DK S7 Edge/Note 5 INSTALL THREAD SMS/MMS working
- Thread starter ExiaGN
- Start date
why is installing this rom so difficult . Is it because its a verizon phone
I noticed I have no data when I am on a phone call. Anyone else have this problem?
Can u send me the kernel link, and should 3g work with ex. slovenia operator ipko ?
Last edited:
On a brighter note videos are uploaded on the main post hope they help
Sent
This is a port from a different country if I am not mistaken so yea its because Verizon uses CDMA not GSM
This is new, I don't experience that at all.
sent
Last edited:
@marblesmike yes, it works on verizon. Unlock bootloader, install twrp recovery using flashify app, then install rom per op. It's a bit of work but totally worth it. MM is way better than KK and LP imo.
may I have the darkera 1.9 lte vzw kernel?
and the sprint one that seems to work so well?
---------- Post added at 12:44 AM ---------- Previous post was at 12:36 AM ----------
and the sprint one that seems to work so well?
---------- Post added at 12:44 AM ---------- Previous post was at 12:36 AM ----------
nevermind I found it
Last edited:
Yea we aren't allowed to post the link here. XDA doesn't allow that kernel don't know why, but that's why its being sent by PM, and also why I don't have it on the main page
Last edited:
So the regular Xposed doesn't work huh. Wasted the better part of the morning figuring that out. Even flashing the remover didn't work. I attempted to flash the sdk23 arm from the main site and even the uninstaller and rebooting just stuck on the pulsating samsung logo. I had to dirty flash the rom again and flash the slim APN and the kernel and the beta supersu from the op and wipe dalvik/cache to get back into my system but all my stuff was in tact. And now I have a fancy reboot menu. 
I'm fairly certain we need the wanam modded Xposed from http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 ( but unsure whether to use the standard marshmallow or the alt meant for the Note 4 variants -- N910F/G/P and Note Edge N915F/G running Marshmallow TW Roms (and given this ported rom despite being on the Note 3 it may need the alt version). REALLY don't want to lose all the time dirty flashing everything again.
I'm fairly certain we need the wanam modded Xposed from http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 ( but unsure whether to use the standard marshmallow or the alt meant for the Note 4 variants -- N910F/G/P and Note Edge N915F/G running Marshmallow TW Roms (and given this ported rom despite being on the Note 3 it may need the alt version). REALLY don't want to lose all the time dirty flashing everything again.
strange, my post didn't take.. I just wanted to update everyone that we in fact do NOT need wanam's alt arm xposed flashable zip, just the regular sdk23 arm one works perfect. It didn't take long to boot up. As a separate issue I noticed I had for some reason uninstalled SuperSU so I just installed that again from the app store (after flashing the Beta from the OP just to be safe) and it asked if I wanted to update the binary and I just let it (normal mode) and I'm happy to say everything works! I have my circle battery icon back! It's the little things.
Nice to know. I have wannams 85.1 and it works fine, but may try the official version on it's next release.
So I've been running this rom for a couple days now and I'm sad to say I'm having major issues with texting. I followed the OP on how to install and was pleased that texting even MMS and 4G all worked properly. But it has come to my attention that I'm missing texts and ones I sent last night only just now were attempted for delivery.. has this happened to anyone else? I'm using a Verizon Note 3 originally bootloader locked retail phone which is now unlocked and I'm in Rhode Island. I'm using the Sprint kernel and like the OP said SPR for the CSC and chose Sprint at boot. Has anyone else had this trouble? Is it just something I should wait out as Verizon becomes more aware/comfortable with me using this crazy phone? I don't like the idea of missing texts.. and it's random. Like 20 minutes ago I sent a text and got a reply immediately, so no worries there.
Back in the day troubleshooting such things on my old Droid using a custom version of CM I was working with devs by sending them copies of my tombstone files, I don't know if Marshmallow even does tombstoning for sms/mms/radio related issues.
BTW I use Google's Messenger app for texting and I'm in Rhode Island.
Back in the day troubleshooting such things on my old Droid using a custom version of CM I was working with devs by sending them copies of my tombstone files, I don't know if Marshmallow even does tombstoning for sms/mms/radio related issues.
BTW I use Google's Messenger app for texting and I'm in Rhode Island.
Last edited:
What were you on before flashing this ROM, just out of curiosity? I'm having random issues too. I came from Alliance ROM 4.4.2.
I came from JasmineROM 6.1 which was running Lollipop rooted. My baseband is OF1 like the original poster in the OP.
I'm thinking it has to do with signal quality at time of sending.. if my signal is poor at the moment, as it is so often for me in weird spots at my apartment and on my commute, I think Verizon puts the message(s) on hold and delivers them after I reboot or something... And I'm not convinced I EVER get messages that were supposed to be sent to me when I was out of range.. like Verizon isn't aware I'm out of range or something and assumes the message came through that I never ever got.
Last edited:
You can try using Verizon Messenger if the stock messenger is giving you issues. but I would say it would be a signal issue. I have been running this now for little over week straight and no issues except in my normal dead zones, but even then I find myself with 1 bar when I should have no service at all, so I wouldn't really say that's a issue more like a improvement.
I've only been on this rom a few days and am not confident about txts either. Once in a while I'll txt myself to see if it's working and have caught the phone not recieving a txt that I sent, with no failed text error on send.
The other thing that's driving me nuts is marshmellow doze putting apps to sleep that I don't want (cf.lumen, aquamail, etc) even after whitelisting them. I really don't want to go back to LP, but am considering it...
EDIT: I use textra btw
The other thing that's driving me nuts is marshmellow doze putting apps to sleep that I don't want (cf.lumen, aquamail, etc) even after whitelisting them. I really don't want to go back to LP, but am considering it...
EDIT: I use textra btw
It's not the messenger, people have sent me screen shots of texts they've sent me and I've not gotten them at all. About an hour ago I was on the phone with my friend in Utah who uses TMobile and my signal dropped to nothing (cancellation circle icon) but it came back on its own. I rebooted just to be safe and called back okay.
Basically it's radio issues for sure... 1) the signal was/is no better than what I had with JasmineROM in the usual deadzones, but 2) I cannot tolerate NEVER GETTING texts that were sent to me, it shouldn't matter whether I happened to have been in a deadzone at the time Verizon should've known and queued it. I think it may be the kernel or something..
I just switched to the vzw kernel (I'm on the 1.9 that you get PM'd by the OP poster if you can't find it on the vietnamese site that was meant for sprint, the spr kernel).
BTW when switching kernels I flash the BETA SuperSU in the OP just to be safe (it's suggested in the original ROM posting elsewhere here) and that removes the SuperSU app but it's no biggie, I just download that again from the play store and it works. I let it update the binary too using the normal method and reboot.
I have a 3rd party Chinese flip cover that works really well when recognized (I love the way it works on Marshmallow) but sometimes it doesn't detect my OPENING the cover. That never happened before. Closing, sure, but not opening. It may be my sensor but a reboot fixes it which I can still do. Just sharing in case others have such issues.
Basically it's radio issues for sure... 1) the signal was/is no better than what I had with JasmineROM in the usual deadzones, but 2) I cannot tolerate NEVER GETTING texts that were sent to me, it shouldn't matter whether I happened to have been in a deadzone at the time Verizon should've known and queued it. I think it may be the kernel or something..
I just switched to the vzw kernel (I'm on the 1.9 that you get PM'd by the OP poster if you can't find it on the vietnamese site that was meant for sprint, the spr kernel).
BTW when switching kernels I flash the BETA SuperSU in the OP just to be safe (it's suggested in the original ROM posting elsewhere here) and that removes the SuperSU app but it's no biggie, I just download that again from the play store and it works. I let it update the binary too using the normal method and reboot.
I have a 3rd party Chinese flip cover that works really well when recognized (I love the way it works on Marshmallow) but sometimes it doesn't detect my OPENING the cover. That never happened before. Closing, sure, but not opening. It may be my sensor but a reboot fixes it which I can still do. Just sharing in case others have such issues.
New posts
-
[APP][2.0+] MiXplorer v6.x Released (fully-featured file manager)- Latest: Sridhar Ananthanarayanan
-
-
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone