I'm not a developer or support any ROMs I just like spreading the good word and helping people when I can. I'm not responsible if your device breaks or you lose data. So make a TWRP backup if you are worried.
This is not a perfect method and it needs improvement so if we can work together and try to fix the issues maybe we can get full support from the OPs' of the note 7 ports.
You must be on MM bootloader, unlocked, rooted, with most recent version of TWRP to ensure everything goes smoothly.
Download most recent Ram Kernel for Verizon:
https://forum.xda-developers.com/note-4/orig-development/kernel-ramkernel-t3472138
Download aurora Verizon data fix:
https://forum.xda-developers.com/showpost.php?p=69066109&postcount=2681
Find a Note 7/S8 ROM that you want to try on the snapdragon note 4 thread:
https://forum.xda-developers.com/note-4/snapdragon-dev
1. Clean install desired ROM (wipe everything 3 times except SD card)
2. Flash datafix
3. Flash kernel
4. Wipe caches and boot into ROM
5. Play around with your new phone lol
If you do not have root for whatever reason download the su zip from nseven thread and flash it in recovery.
https://forum.xda-developers.com/note-4-verizon/development/note-4-grace-7-t3434155
These ROMs do not support Verizon apps including visual VM and MyVerizon. They also don't support Wi-Fi calling. Check the bugs of the ROM so you know what to expect.
If you are having issues check the original ROM thread for answers or post a question on here and maybe somebody can help.
The bugs that I know so far that are Verizon specific across all ROMs:
- MMS does not work on the stock messenger (*See below for fix)
- Phone FC when the person on the other end hangs up first (really want to figure this one out)
- Texts are sometimes delayed for some reason
Some ROMs might require you flash gapps for some reason so follow the op instructions for the ROM you choose, just ignore any modem or bootloader flashing instructions.
I've tried Norma ROM and Racerom. I've had the best experience with Racerom but that is just my personal preference. Any questions please ask.
Cheers!
Thanks to @chevyrhoads for all his time and effort on nseven. I cannot thank you enough sir! And thanks to all the other developers sharing these great roms, data fix, and kernel for everyone to enjoy.
MMS Fix:
1. Extract others.xml from nseven ROM found in system/csc folder and save it to your SD.
2. Edit the others.xml file and delete everything within the <FeatureSet> tags.
3. Paste this feature within the <featureset> tags:
<CscFeature_Message_ConfigMmsMdnTagName>X-VzW-MDN</CscFeature_Message_ConfigMmsMdnTagName>
and save the changes.
4. Paste the others.xml file in your current ROMs system/csc folder (In my case there was no others.xml file to swap or replace) and change the permissions of the file to 644 and reboot.
5. You should now be able to send MMS on the stock messenger app !
hey i flashed unchanced rom and the data fix + kernel but my phone still reboot if i use data
How did you fix the fc after phone call. Also, my phone shows 3g all the time and my text.mwssafes seem delayed. Im using Verizon note 4 n910v
I tried Race Rom and get a repeated Phone has crashed. I had better luck with the Norma ROM but had severe battery drain and after being off for a while, the phone wont turn back on, requiring a battery pull.
Any suggestions on the best ROM to try?
Sorry for not responded sooner
derSA7 said:
hey i flashed unchanced rom and the data fix + kernel but my phone still reboot if i use data
Click to expand...
Click to collapse
I guess that ROM does not work with this setup I'm sorry.
jBMWguy said:
How did you fix the fc after phone call. Also, my phone shows 3g all the time and my text.mwssafes seem delayed. Im using Verizon note 4 n910v
Click to expand...
Click to collapse
I cannot figure out what causes the phone fc. Maybe try flashing the 4G fix found on chevyroads nseven thread. I did notice that texts are delayed. After using racerom for a couple of weeks I've been getting reboots, freezes, and some texts not going through for a very long time. I recently flashed RR 7.1.2 but having issues with recording Snapchat videos so I'm probably going to go back to nseven tonight or tomorrow. I will add delayed texts to the bugs list.
bishop0114 said:
I tried Race Rom and get a repeated Phone has crashed. I had better luck with the Norma ROM but had severe battery drain and after being off for a while, the phone wont turn back on, requiring a battery pull.
Any suggestions on the best ROM to try?
Click to expand...
Click to collapse
From what I see Norma has the most potential on the snapdragon thread but idk after using racerom for weeks it started falling apart on me. I would now honestly recommend using Nseven for a note 7 port. I'm gonna keep this thread open so tinkerers/crack flashers can mess around and report their findings on here and maybe we can get a more stable method.
Sent from my SM-N910V using Tapatalk
jcip17 said:
Sorry for not responded sooner
I guess that ROM does not work with this setup I'm sorry.
I cannot figure out what causes the phone fc. Maybe try flashing the 4G fix found on chevyroads nseven thread. I did notice that texts are delayed. After using racerom for a couple of weeks I've been getting reboots, freezes, and some texts not going through for a very long time. I recently flashed RR 7.1.2 but having issues with recording Snapchat videos so I'm probably going to go back to nseven tonight or tomorrow. I will add delayed texts to the bugs list.
From what I see Norma has the most potential on the snapdragon thread but idk after using racerom for weeks it started falling apart on me. I would now honestly recommend using Nseven for a note 7 port. I'm gonna keep this thread open so tinkerers/crack flashers can mess around and report their findings on here and maybe we can get a more stable method.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
All of the phone FC's people are experiencing from the Note 4 S7/S8 ports, are due to the method / files along with the porting process to enable the S7/S8 ports to work with the Note 4's.
If you notice, you only receive a FC if the other party hangs up or disconnects first. If you "beat them to the punch" and end the call before the other party does, you won't receive the FC.
Another thing to note; when using a third party app for text messaging such as "Textra" for example. Let's say you are using Textra to text back and forth with someone and suddenly you decide to call them. If you use Textra's built in function to initiate the call, it doesn't matter if you are first or last to end the call, you won't get a FC. I've actually tested that theory out for another developer per their request, and was able to make calls with no FC's regardless of who ends the call first, just by opening Textra, and choosing to call someone from it's built in feature.
Just an FYI...
I'll possibly be taking over all future development for chevyrhoads, in reference to the Nseven ROM per his and my discussion just as soon as I'm back in the states, caught up with all the kids in college and school activities, kiss the wife, and feed the dogs, lol. I'm no android developer, nor am I pretending to be. "I'm only an android enthusiasts, and happy to be one." Retired Senior Software & Security Expert / Software Developer / SEAL, will do my best to keep the Nseven ROM up to date for everyone to enjoy...
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
p.s. @jcip17,
Those are some of the best & well written instructions I've come across. Excellently done!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Android.Ninja said:
All of the phone FC's people are experiencing from the Note 4 S7/S8 ports, are due to the method / files along with the porting process to enable the S7/S8 ports to work with the Note 4's.
If you notice, you only receive a FC if the other party hangs up or disconnects first. If you "beat them to the punch" and end the call before the other party does, you won't receive the FC.
Another thing to note; when using a third party app for text messaging such as "Textra" for example. Let's say you are using Textra to text back and forth with someone and suddenly you decide to call them. If you use Textra's built in function to initiate the call, it doesn't matter if you are first or last to end the call, you won't get a FC. I've actually tested that theory out for another developer per their request, and was able to make calls with no FC's regardless of who ends the call first, just by opening Textra, and choosing to call someone from it's built in feature.
Just an FYI...
I'll possibly be taking over all future development for chevyrhoads, in reference to the Nseven ROM per his and my discussion just as soon as I'm back in the states, caught up with all the kids in college and school activities, kiss the wife, and feed the dogs, lol. I'm no android developer, nor am I pretending to be. "I'm only an android enthusiasts, and happy to be one." Retired Senior Software & Security Expert / Software Developer / SEAL, will do my best to keep the Nseven ROM up to date for everyone to enjoy...
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
p.s. @jcip17,
Those are some of the best & well written instructions I've come across. Excellently done!
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Thank you @Android.Ninja ! You made my day with this post. If you need a tester or any assistance please just ask. I'm a decent problem solver lol. Also that is a great find using textra call feature doesn't FC the phone. We must keep these great phone alive!! If it's possible I ultimately would like to create a perfect datafix for all these ROMs so we are free to choose any port. I'm positive it is not as easy as it sounds but it's wishful thinking. I figured out which CSC feature enables mms on the stock messenger. I'll post it in the OP.
Sent from my SM-N920V using Tapatalk
Replied to the OP instead of editing it. Disregard this post lol.
jcip17 said:
Thank you @Android.Ninja ! You made my day with this post. If you need a tester or any assistance please just ask. I'm a decent problem solver lol. Also that is a great find using textra call feature doesn't FC the phone. We must keep these great phone alive!! If it's possible I ultimately would like to create a perfect datafix for all these ROMs so we are free to choose any port. I'm positive it is not as easy as it sounds but it's wishful thinking. I figured out which CSC feature enables mms on the stock messenger. I'll post it in the OP.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
That sounds great, referring to the CSC! I'll put you on the Alpha/Beta Testers list as soon as I can. We may be able to get together and create a universal one in all datafix using aroma installer to allow the user to "Select" the ROM they would be using. The only issue would be of there was a major platform upgrade by the developer of the ROM of their choosing, but even so, we could just have it "Null Out" as to not harm or change anything etc. Yup I've got many of these note 4"s best phone for the money IMO.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Anybody experiencing lockups every once and awhile on any of the ports where you need to pull the battery? And when the phone boots up texting does not work until a proper reboot is performed? I was almost late to work today because my phone locked up overnight and that is my alarm lol. I'm back on nseven to see if its the ports or my phone :/
From what I remember this started when I was using resurrection remix 7.1.2 and ever since I've been having lockups on the other n7 ports.
Sent from my SM-N930V using Tapatalk
jcip17 said:
Anybody experiencing lockups every once and awhile on any of the ports where you need to pull the battery? And when the phone boots up texting does not work until a proper reboot is performed? I was almost late to work today because my phone locked up overnight and that is my alarm lol. I'm back on nseven to see if its the ports or my phone :/
From what I remember this started when I was using resurrection remix 7.1.2 and ever since I've been having lockups on the other n7 ports.
Click to expand...
Click to collapse
I'm interested in nseven Rom and heard good things about it. Could you suggest it as a daily? I'm on kyubi note 5 port.
jafferkhan said:
I'm interested in nseven Rom and heard good things about it. Could you suggest it as a daily? I'm on kyubi note 5 port.
Click to expand...
Click to collapse
That's nice to hear you're on Kyubi, thats my baby. There are some minor-ish issues with nseven, t9 dialing does not work, the auto brightness does the opposite of what it's supposed to do (sunlight dims the screen, darkness makes the screen brighter), fingerprint doesnt work, and always on display causes a brightness issue where you cant control the brightness (just untoggle AOD and brightness can be controlled). And for me I've been having intermittent issues with data where my 4g icon blinks white then dims to grey then back to white nonstop. When this happens I cannot use data until I reboot. Other than that the note 7/s7 software is awesome and everything else works from what I can tell. How's Kyubi running for you? I kinda miss it lol
Sent from my SM-N930V using Tapatalk
jcip17 said:
That's nice to hear you're on Kyubi, thats my baby. There are some minor-ish issues with nseven, t9 dialing does not work, the auto brightness does the opposite of what it's supposed to do (sunlight dims the screen, darkness makes the screen brighter), fingerprint doesnt work, and always on display causes a brightness issue where you cant control the brightness (just untoggle AOD and brightness can be controlled). And for me I've been having intermittent issues with data where my 4g icon blinks white then dims to grey then back to white nonstop. When this happens I cannot use data until I reboot. Other than that the note 7/s7 software is awesome and everything else works from what I can tell. How's Kyubi running for you? I kinda miss it lol
Click to expand...
Click to collapse
That's a great analysis bro. Thanks for the feedback I really appreciate it. Kyubi is the best Rom for this phone period. I've tried all of them except nseven but kept coming back to kyubi because of its stability. It's fast, smooth and very good on battery. I missed the note 5 themes which I get here plus the theme store and more. I think kyubi is more of what a stock Rom should have been. I know it's developer is very good, everything works flawlessly, I've had zero issues on it since its almost 9 months that I've been using it. Close your eyes and flash it, it's that good!
Testing....
Sent from my SM-N930V using Tapatalk
I'm on Verizon now and if I get another VZW N4 I'll build a proper N7 or S8 rom with everything working as it should. other than Iris scanner and fingerprint scanner.
But just know that these international port Roms are not setup for the CDMA networks so they will not work right. Even these "fixes" are only partial things that are missing and there's more smali framework edits needed to make them work right. The best option is to build a Rom using the actual VZW software and this will solve most all of these issues. Been there done that with my UN5 and UN7 Roms. I have the S7 edge now but to be honest I'd much rather go back to the N4 running my ported N7 rom so I can have my IR blaster and removable battery. The N4 is the best phone in my opinion.
note 4 is died and is a new way to do this fast and easy
Related
Hi buddies
As Grarak chose to close the thread of his rom and that maybe some of you want to have some more return and exchanges about the way the rom works, discuss about bugs etc, i open this thread, so that we will be able to do what a forum is done for : talk and exchange together.
New version is 12082014, any return?
Testing soon..
Is calling with sim 2 in 2g working Now?
If not how to use it Any tetsters!
Edit :still No sound from sim2
and there is No way to chose network type
and No 3g from sim 2 too
Im on 9-12-14 build....2g sim not working same as official cm11....3g sim is working......
i 've had terrible battery life, and searching on google lead me to a battery misc processus eating battery, problem solved with 5.0.1 by google
do you guys have the same experience, and have heard about a fix incorporation in the new builds? :good:
I had to go all the way back to the 11-20-14 build. I tried updating to the new builds 12-8, 12-9 and 12-10. No data at all on any of these builds.
Flashed the newest build! We're on Lollipop 5.0.1 now This update is supposed to help battery life. We'll see.
The new music app automaticaly force closes, and the DSPmanager was replaced with AudioFX.
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
fabulous69 said:
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
Click to expand...
Click to collapse
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
FoxyDrew said:
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
Click to expand...
Click to collapse
mhm then i think a change that has broke the app. I m sure Grarak will correct it in the next release
Ok, the ROM was going great for me, then yesterday at work my phone turned off when it was in my pocket. I tried turning it on, it booted, started doing the boot animation and then did that for five minutes before it shut off again. This time it wouldn't turn back on no matter how many times i tried power cycling or booting into bootloader. When I got home I tried charging it and the light wouldn't even come on. So I plugged it into my PC and the phone showed up as qhsusb_bulk. After researching that i found it means the bootloader got wiped somehow. My question is, how could my bootloader be gone, because as far as I know, no one has gotten their device S-OFF.
your device is bricked
seems there is a solution on the web but not working for everybody and for specific devices
i dont know what to advice you...
i dont know if it is rom related, but if it is, i wont flash this !
Yes that's what i figured. Luckily Amazon was nice enough to give me a new phone once I send that one in. I was just trying to figure out how it would even be possible that my bootloader got fried, considering my device was still S-ON.
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
DRAGONMM2010 said:
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
Click to expand...
Click to collapse
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
Completely agreed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
fabulous69 said:
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
Click to expand...
Click to collapse
Didn't test it. Haven't spent enough time on Lollipop because of the no data issue.
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
thirteen_percent said:
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
Click to expand...
Click to collapse
Yah data works...just not good. It has to do with not being able to access APN's.
No one want's to sit "for a WHILE" to open a webpage or read an email.
On the latest build, System UI crashes.
I'm going to download it tonight and test it out. Hopefully, the massive bugs were fixed and we can have OFFICIAL Cyanogenmod 12 on our devices.
I just randomly checked yesterday and noticed it was back. I'm on 03/27 right now and so far, so good.
Sent from my Sprint Galaxy S5.
Is everything working?
daniel3x said:
Is everything working?
Click to expand...
Click to collapse
It seemed to be. Calling, wifi, data (3g and LTE), SMS and MMS were all working for me. I opened Maps and the phone froze, so not sure if GPS is working. I flashed back to another rom though.
GPS works just fine.
Sent from my Sprint Galaxy S5.
Does anyone have a visual voicemail apk that works by any chance? If you do, please pm it to me or something, I'd really appreciate it, thanks!
JSarella said:
Does anyone have a visual voicemail apk that works by any chance? If you do, please pm it to me or something, I'd really appreciate it, thanks!
Click to expand...
Click to collapse
Check PM
CM12 Noob
Nor sure if anyone is still following this post but I installed cm12 a few days ago and the only issue I can reproduce it the Bluetooth cuts out. I can't complain, it's way faster than touchwiz and it does not crash any more frequently. One issue I have noticed is that it doesn't seem to download MMS automatically but I've only noticed it when receiving a group txt in hangouts. I can't seem to find any good discussion groups on cm here on XDA. If anyone has a suggestion, I have a Spring Galaxy S5 and am quite new to flashing as well as forums, but pretty proficient with computers. Any help would be appreciated, Thx
If CM 12 is broken i dont receive calls but can do it, It is best to install MOAR
Bluetooth does not work , the messages are closed every 5 minutes
Need working Sprint Visual Voicemail apk for Galaxy S5 running Fusion Rom
I apologize if I am posting this in the wrong area. I have been running the Fusion Rom on my Sprint Galaxy s5. I love it, but cannot get any voicemails! Have tried a few apks, but no luck. Any info and/or download links would be very much appreciated!!
Susan
I just tried the 8/8 build. So far, pretty stable. I did try the full device encryption and it basically borked the installation. I got it to come back by clearing cache a few times (why a few times and not just once? Who knows.) but it was increasingly unstable at that point (random crashes, random boot freezes). I wiped and reinstalled and it's back to stable, so it's definitely the encryption. Going to mess with bluetooth today to see if that's been resolved yet.
Bluetooth still completely doesn't work. I can't even get it to connect. Not quite ready for prime time I guess.
So at this point, not worth trying? no BT? How's the camera?
TN 12.1 latest build
I have been running the 9/26/15 build for three days and am experiencing the worst battery drain since the day this phone came to market.
I am wondering if this is a TN problem or the latest lollipop aosp issue as a whole?
Thanks
im using Team Nocturnal vm_kltespr-userdebug 5.1.1 lvy48f0333148f75 test keys build date 9/13/2015 and I adjusted the i/o-scheduler and have stopped charging my phone over night... it lasts all day with tons of emails and some multimedia a few dozen phone calls and 150 texts and all night and I charge it in the car between work and home... approx 45 min... good to go.... the only thing that doesnt work is the fingerprint scanner... everything else is fine... it does have trouble switching data back to mobile off of wifi, but, nice smooth and fast...
misile2012 said:
im using Team Nocturnal vm_kltespr-userdebug 5.1.1 lvy48f0333148f75 test keys build date 9/13/2015 and I adjusted the i/o-scheduler and have stopped charging my phone over night... it lasts all day with tons of emails and some multimedia a few dozen phone calls and 150 texts and all night and I charge it in the car between work and home... approx 45 min... good to go.... the only thing that doesnt work is the fingerprint scanner... everything else is fine... it does have trouble switching data back to mobile off of wifi, but, nice smooth and fast...
Click to expand...
Click to collapse
What i/o settings are you using?
Sent from my SM-G900P using XDA Free mobile app
Q&A for [MAR 27][WEEKLY][ROM][UNOFFICIAL] CM 12.0 for Samsung ExpressATT (SGH-I437)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MAR 27][WEEKLY][ROM][UNOFFICIAL] CM 12.0 for Samsung ExpressATT (SGH-I437). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
galaxy express i437
davideddu96 said:
I'm so sorry you guys won't be able to see CyanogenMod's april fools day prank, today's build doesn't boot because of the camera patches :/
But attached a picture of what you've missed
I'll try to add it to the next working build
You should have seen my face when I saw it [/QUOT
i been following this post since it began ....been using cm 11 from the previous thread havnt trd cm 12 yet for this fone ...but gettin ready to ...since i dnt have many post ...well ya know...keep up tha good work ...thanks
Click to expand...
Click to collapse
galaxy express i437
tha only real problems i have had.is with the.wifi actin alil buggy at times ..i have no idea why ..i do have a 437p model but i dnt think that has anything to do with it ...i am runnin cwm recovery 6.0.4.6. ..and cm 11 ...but every thing else works fine ..the only app i had trouble with is talkatone ..people cudnt hear me talk ..i cud hear them just fine ..like you were sayin somethin about the mic not workin ..that maybe tru..i thougt maybe my wifi was actin up ...any advice wud be appreciated ..thank
Great ROM!
Beautiful ROM man, I'll be following the development. I'll test out a couple of fixes I found from beta testing my ancient Optimus S.
I posted directly to the blog, but I like following on the forums better
Quickest install I've ever seen.
No problems on NOOP. No lag that I notice.
One question, for the masses or developer. Any thoughts on how to root this sucker? I did the "sustain root" on CWM, I switched the root access on the settings to ADB and app.
Can't figure out how to get root though. Thrown various APKs at it, everyone gets a blocked install (third party apps is enabled too).
Easy root? and minimal Gapps working
Greetings all,
I tested this app package, it's much smaller than the primary app package. Store is working, no errors thrown up. Yet, I've been running for about 30 minutes now, and installed root checker, again, no errors. 5.0 is tested.
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Just don't like all the goole news, games, and music crap that comes with a full GAPPS package.
Comes from working on the LG Optimus project.
Also, am I going crazy, or did I just switch a toggle and get root access?
Seriously? No ADB, no chinese programming? Just handed me root access like it was nothing?
Friggin awesome.
Camera Fix
I got the camera to work better.
I had to use
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
In case this blog block the link, it’s Open Camera by Mark in the play store.
I have working video and pic on the rear camera, and the “selfie” front camera works for picture only. In video mode, It duplicates/tiles video. That’s the only thing.
Other than that, very few problems. Pretty zippy in terms of speed. Course I came from the LG Optimus S, so anything is zippy to me. Noop works good.
Annoying though that it seems to only save nandroid backups to some mysterious "secure" folder. I've looked for it, can't find it. Maybe it's just ROM Manager being a jerk though.
Why haven't you updated the ROM since April 24?
You are alive? Yay!
Very excited for the next build to go up, can't wait! Welcome back!
Sent from my SAMSUNG-SGH-I437 using Tapatalk
FruG3rT said:
Very excited for the next build to go up, can't wait! Welcome back!
Sent from my SAMSUNG-SGH-I437 using Tapatalk
Click to expand...
Click to collapse
Me too. It's going up later this morning.
Sweet, looking forward to notifications on my lockscreen. Going to have to swap out the font for the clock though, Roboto looks weird when thin.
Thanks for taking the time to build this for us.
I didn't build this. But be warned, Telephony, bluetooth, camera, and flashlight doesn't work.
Mostly nitpicking, but after about an hour of testing, here's what I found, on 12-20150424:
Telephony requires a two+ rings prior to the other phone ringing at all. May be a carrier issue.
The Location quick setting tile for the notification drawer disappears when accessing the tiles from the lockscreen, at least with a pattern lock. Unaffected are WiFi, mobile data, Bluetooth, tethering/hotspot, airplane mode, rotation control, flashlight, AudioFX, ADB over network, Compass, battery mode, color inversion, LTE
, LiveDisplay, NFC, screen timeout and profiles. (logcat for disappearing tile: pastebin.com backslash 4Ny6rR58)
Compass in said notification drawer does not function correctly, tilting devices does not equal change in heading. i437 hardware issue?
SMS is vulnerable to Stagefright, as expected of pre-August 2015 builds.
Settings > Storage: Overflow menu option 'USB computer connection' activity never starts if phone is not plugged into computer. IMO, should offer options even if not connected.
Cannot remove guest user under Settings > User without first being ON guest account.
Camera findings:
Rear camera 4.9 mp pictures do not preview correctly in camera app, appear as pure gray. Opening files with third-party app resulted in expected photo.
720p rear camera never saves video; must lower resolution to function. In addition, appears R and B channels get swapped in preview.
Beyond those, no complaints so far, and been using this for about two months now. Any bootloops are the result of an improper Xposed installation
(please don't stop making this, it's much fun to poke and prod D:)
WiFi radio not working
Hey guys, so I have a Samsung Galaxy Alpha that I rooted and flashed CM12.1 along with Gapps on to it and it worked fine. Then I flashed my aunt's Samsung Galaxy Light SGH-T399 with CM12.0 too (with Gapps) and again everything worked fine including WiFi except that she had no service from her provider but still could receive calls but neither call nor Message. So I flashed a new radio (SGH-T399N) which I found somewhere in the discussion page and everything worked! She now got service, meaning she could make calls and message too.
Now I flashed my uncle's Samsung Galaxy AT&T SGH-i437 along with Gapps and again, everything worked including Camera (Google Camera not stock). Except the WiFi. When the CyanogenMod set up screen loaded and asked for my preferred language I chose English as always but when the WiFi screen popped up, it simply said "WiFi turning on" but it didn't! For 10 minutes I sat there waiting for it to enable but no such luck. So I skipped ahead to the home screen and I noticed that Mobile Service worked 100% for the phone. So basically, is there a WiFi radio I must flash for the WiFi to turn on? Right now I just downgraded him to CM11 KK 4.4.4 with Nova Launcher and the WiFi is enabled. Thanks in advance!
tl;dr WiFi doesn't turn on SGH-i437, mobile service does. Any radio or something I need to flash?
Hey silents090,
I have a sgh-t399, any chance you could forward me the link for cm12 you got working on your relatives? cuz I flashed cm12 and had issues with mobile carrier, and regular sms texts....
thanks in advance
coolfake17 said:
Hey silents090,
I have a sgh-t399, any chance you could forward me the link for cm12 you got working on your relatives? cuz I flashed cm12 and had issues with mobile carrier, and regular sms texts....
thanks in advance
Click to expand...
Click to collapse
Sure,http://forum.xda-developers.com/android/development/rom-cm12-light-beta-t3154688
Flash this rom on TWRP recovery, then flash this radio right after flashing the rom also using TWRP. http://forum.xda-developers.com/attachment.php?attachmentid=2978028&d=1413801605
you rock! excited to try cant wait, id hit the thanks button but I m a noob and couldnt find it. so do I need to do gapps package with these? if so im assuming I do it last? and is your aunts galaxy light run into anu major issues?
coolfake17 said:
you rock! excited to try cant wait, id hit the thanks button but I m a noob and couldnt find it. so do I need to do gapps package with these? if so im assuming I do it last? and is your aunts galaxy light run into anu major issues?
Click to expand...
Click to collapse
Yep you need to flash gapps after the radio
here's a link: http://opengapps.org/?api=5.0&variant=nano
Also nope the phone hasnt had any issues! Just make a backup in twrp to be safe though
always do(make a backup). so I flashed the cm12 then the radio. but my screen stops working... so had to flash back to my stock. was ur aunts a pcs sgh-t399 or tmobilw
coolfake17 said:
always do(make a backup). so I flashed the cm12 then the radio. but my screen stops working... so had to flash back to my stock. was ur aunts a pcs sgh-t399 or tmobilw
Click to expand...
Click to collapse
it was a T-Mobile t-399
Out of curiosity, which version of the rom did you use? I used vanilla.
Secondly, does the rom work when you do not flash the radio?
Thirdly and lastly, you clear the cache, data, dalvik etc before flashing, right?
UPDATE: The ROM has been updated to version 2 where lot of bugs have been fixed!
First things first:
The ROM is strictly for those who are using an unlocked N910P on a GSM SIM globally!
This ROM has been ported by @anggara08 for the Snapdragon Powered Galaxy Note 4. He is the creator of this ROM and I'm only sharing the thread link here so that N910P users (which is generally not supported by the OP of original thread) can take a look at what this ROM has to offer.
I'm in no way associated with the ROM development & all the credit for the work goes to @anggara08.
Now, let me come to the main motive of why I am creating this (or sharing this thread) here on N910P thread...
The ROM is being developed keeping in mind the F & G variants of Note 4. However, I did download the ROM on my N910P and it booted successfully. The ROM has few bugs right now like Bluetooth, Flashlight, Hot-Spot cannot be controlled by the toggles, but certain workarounds have been posted by the some users which make this ROM a must try.
So, coming directly to the procedure for flashinf it on N910P:
1. Head over the following thread & read it properly with proper concentration to save your's as well as others time to solve problems that can or could have been avoided.
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-t3440223
(All credit goes to @anggara08)
2. Download all the fixes posted by OP like camera-fix, & lock-screen fix.
3. Do note that the boot-loader & the modem required is PE2 or PG1 (I have tested it on these personally). Any other version does not work like OG5, OK1, PE1,etc.
4. Take a full back-up of your current ROM.
5. Make proper wipes (system, dalvik, data, cacke, internal memory,etc).
6. Flash the downloaded X-ROM. Once the flashing is finished, the ROM will automatically boot without any prompt from the TWRP Recovery.
7. It will take a long time to boot. My suggestion is to keep the phone plugged to a charger while the process is going on so as to prevent battery drain.
There's absolutely no need of flashing any Kernel or Super-SU or anything.
Let the ROM boot first.
8. Once it boots, you'll notice that there will not be any network. For it, you have to download following data fix:
(The zip file is as an attachment at the end of this post, Credit goes to @boot_sect for posting it)
9. Boot into TWRP & flash the Data-Fix. Reboot to the ROM and the network will be there. (Note: I am a GSM SIM user so the fix worked for me. Sprint users, try this out at your own will & risk.)
10. Once the ROM is up & running, flash the respective fixes (as mentioned by me earlier & available on original thread by OP) and you'll have an amazing ROM to play with. :good:
Few suggestions & fixes by @boot_sect:
Additional Notes:
Bluetooth not turning off: Seems to be ROM issue, or at least for us T/W8s. Even without data fix it does not want to turn off...
> Temp fix: Quick and dirty way to disable bluetooth is by going into your favourite app manager (eg. Titanium Backup) and disabling "Bluetooth Share", then re-enabling when bluetooth turns off. This will keep BT turned off until you manually enable it next time (or at least, for a very long time.)
Flashlight not turning off. Most likely ROM issue as many users are experiencing this.
> Temp fix: Use "Quick Tools" in the Edge Panel to turn it off. Thanks to @justforgot to finding this workaround.
I'm not posting any screen-shots of the ROM as a dedicated video of it on N910F can be found on the original thread.
Last but not the least, If moderators find this thread useless, they are free to close it.
@Robin...Thanks for hooking us up to this and taking time for the right up.
Sent from Nowhere
how long we have to wait?
how long we have to wait for the first boot?..and thanks
Was able to boot it up and play with it but no go on the data for sprint. I tried manually setting apn and nothing also the screen goes dim after a while. Nevertheless it is awesome seeing this thing running and cannot wait for the geniuses to stabilize it. One awesome thing I noticed it is how little bloat it had almost no apps aside from the essentials.
abel1233 said:
how long we have to wait for the first boot?..and thanks
Click to expand...
Click to collapse
It should not take more than 15-20 mins... If it does, pull out the battery (though not recommended in first place) and try again.
innthesun said:
Was able to boot it up and play with it but no go on the data for sprint. I tried manually setting apn and nothing also the screen goes dim after a while. Nevertheless it is awesome seeing this thing running and cannot wait for the geniuses to stabilize it. One awesome thing I noticed it is how little bloat it had almost no apps aside from the essentials.
Click to expand...
Click to collapse
Did you not get the data or the network??
Also,did you flash the data-fix for the network or it was available without flashing it?
As far as the bugs are concerned, I can help you out for a work-around.
Hello,
Was anyone able to fix the screen going dim?
robinhood1808 said:
Did you not get the data or the network??
Also,did you flash the data-fix for the network or it was available without flashing it?
As far as the bugs are concerned, I can help you out for a work-around.
Click to expand...
Click to collapse
I did not get data or network. I did flash the fix but it did nothing.
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
tx_dbs_tx said:
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
Click to expand...
Click to collapse
Can't wait for the S7 note 5 port! Check back daily for it!!!! ????
tx_dbs_tx said:
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
Click to expand...
Click to collapse
i can't wait for your rom!!
they are usually the best ones!!
@tx_dbs_tx: You are absolutely right that each and every developer works extremely hard in order to make a ROM boot. We should be really grateful to all the developers like you who make it possible for the users like me to experience difference ROMs on our phones.
It would be really shameful on our part if we can't even thanks a developer for all the hard work that he puts in..
Also, I'm using a GSM SIM (had even contacted you some time ago regarding it, if you remember.. ) on N910P so the above mentioned ROM worked for me without any network issues. I've edited the thread to mention that It's only for those who use GSM SIM on N910P.
tx_dbs_tx said:
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
Click to expand...
Click to collapse
I must say I was not expecting to even boot at all and was surprised when it did. I totally agree with the patience, I use your roms regularly and in fact am using one as we speak and loving it. Many thanks for your time and dedication, it very much appreciated.
I am here to say a BIG thank you. This Rom is working very well, just a few bugs like the bluetooth not turning off and a few other minor things.. Keep up the great work look forward to this Rom progressing.
Droidman61 said:
I am here to say a BIG thank you. This Rom is working very well, just a few bugs like the bluetooth not turning off and a few other minor things.. Keep up the great work look forward to this Rom progressing.
Click to expand...
Click to collapse
You got sprint LTE working?
Cool, will have to check out. I'm also an unlocked gsm user, and am always having to tweak build prop and apn conf files to get my ROMs working properly. Not that I mind.
But cool to see something else to try. Thanks
Awesome Dude
tx_dbs_tx said:
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
Click to expand...
Click to collapse
Your Rom is Amazing btw.
Successful
Im instal successful note 7 rom for note 4P
But im new member, i cant post my youtube chanel
youtu.be/ODPbW6S5yEU
Look more there
duc501613 said:
Im instal successful note 7 rom for note 4P
But im new member, i cant post my youtube chanel
youtu.be/ODPbW6S5yEU
Look more there
Click to expand...
Click to collapse
Would be a great daily ROM once 3g or 4g works!?
Sent from my SM-N910P using XDA-Developers mobile app
jglm4u said:
Would be a great daily ROM once 3g or 4g works!
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
3G working, vietnam haven't 4G yet
Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.
If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.
DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads
Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.