Hello everyone.I wanted to briefly comment and requests on the development of safestrap.
I would like to start by commenting on the bloating of sfaestrap.6 rom slots?Why have all these rom slots when we cannot even really install roms on slots other then stock/slot1/slot2?Not to mention the available space for those extra slots would not be effective enough other then for testing purposes, which honestly i would use rom slot2 for that.Reason for this comment is available space.6 roms slots is a tease and also congestive looking in the safestarp ui.
My request would be more towards removing those un-needed extra slots, and most importantly adding more STOCK SLOT-support.Meaning when i install a rom on stock slot i would like all available space on my internal storage.Not left over fragments of the firmware install hanging around collecting dust in my internal storage, i want all that internal storage available for the rom i install, if this is possible.
Reason is XT910 is getting old and i would just like a fully working kexec supported rom on stock slot 100%, and slot1 & 2 usable for testing purposes.I think this clean up and added support for stock slot would be a hugh advantage for the future appeal of the XT910 as it begins it's death and rebirth to kexec based roms.
are you sure you are "requesting" and/or "suggesting" features? because it doesn't look like it, more like you are ordering stuff for yourself? I hope you know developers are not hired and payed here to make you an all working ROM.
This thread is about safestrap not roms.
Sent from my XT910 using xda app-developers app
This thread needs closed.
Sent from my XT912 using Tapatalk 4
This thread would belong to the "General Section" please post only development related threads to the Development Section
Related
LETS GET THIS LIST GOING!!
I know there are several threads on this allready, but finding the actual information of which roms work and which don't is very hard, so I've decided to make this thread to have a centralized place to list and discuss roms that work with the patch.
First things first:
The verizon patch and information about it can be found here. http://forum.xda-developers.com/showthread.php?t=2055218
Things to remember:
Do Not flash modems from any rom that doesn't have a Verizon Base.
Always make a backup before testing the patch with new roms.
(not sure if kernels are harmfull, or if you need to flash specific verizon kernel after flash, will update when I gather more info, for now this is a list of known working roms and how you got there.
Now the Good Stuff.
I thought since I was making this thread I would jump in and test first. here's what I have so far.
1) Ok, my first attempt wasn't so good. I installed the whompasaurus rom from the sprint forum. Device booted fine, but upon boot I got an Ecryption Failed screen with no way to go any further (to my knowledge anyway) I feel this is stll relevant to the thread. So post your experiences and I will update the op accordingly. I have seen a few roms on the at&t forum that say "no device check" therefore I assume they will work. Time will tell.
Please feel free to list roms that you have succesfully got working with the vzw patch and if you used build prop edits to achieve this as well then please be specific and I will add them to the op as they come in.​
Ive got all the DLL1 and DLL4 roms to work in the att & tmobile forums.
The caveat with Scott's patch is that it is only designed to get TW roms from other carriers working on our devices. While most TW roms will boot fine after the patch, they will more than likely require some build.prop modification to get them completely up to snuff. In the case of porting AOSP roms, the patch isn't entirely useful, save for a few vzw specific system applications, as AOSP doesn't use CSC files. AOSP porting can be done with build.prop adjustments.
Can you elaborate on which build prop edits need to be done, ro.product.model, etc. As I stated above I tab into an encryption problem, would a stock Verizon build pro fix that?
Sent from my SCH-I605 using Tapatalk 2
Jsminnis please add me on gtalk. [email protected]
There is a script with claims to odex a deodexed rom via a flash able script here for those who are interested
http://forum.xda-developers.com/showthread.php?t=2095922
[Script] Amestris Odexer V3.0 [4.1.2] Optimize your phone!
Is it possible for ROM-Creators who are using Aroma (like NeatRom by sale,where I originally liked to post but have not enough posts yet) to include this script into Aroma installer?
Reason for the question is the constant demand of different modifications for guys like sale, so instead to have time further optimizing their roms, providing custom versions of one rom for special demands could be avoided with a possibility like this.
Do not want to start a discussion about pro&cons of odex/deodex and zipalign as theres plenty to read on that topic online.
So let devs concentrate on optimizing their roms and users decide which color they think they need?
Please forgive me if I got something wrong, overlooked a post somewhere or just used the wrong keywords to search on that special topic
Would be happy with a short, technical answer if it is possible or not and why.
FosCoJ said:
There is a script with claims to odex a deodexed rom via a flash able script here for those who are interested
http://forum.xda-developers.com/showthread.php?t=2095922
[Script] Amestris Odexer V3.0 [4.1.2] Optimize your phone!
Is it possible for ROM-Creators who are using Aroma (like NeatRom by sale,where I originally liked to post but have not enough posts yet) to include this script into Aroma installer?
Reason for the question is the constant demand of different modifications for guys like sale, so instead to have time further optimizing their roms, providing custom versions of one rom for special demands could be avoided with a possibility like this.
Do not want to start a discussion about pro&cons of odex/deodex and zipalign as theres plenty to read on that topic online.
So let devs concentrate on optimizing their roms and users decide which color they think they need?
Please forgive me if I got something wrong, overlooked a post somewhere or just used the wrong keywords to search on that special topic
Would be happy with a short, technical answer if it is possible or not and why.
Click to expand...
Click to collapse
I don't think any dev would be willing to incorporate this due to the number of problems it would cause.
If you read the relevant thread you can see what a hit and miss affair doing this is.
slaphead20 said:
I don't think any dev would be willing to incorporate this due to the number of problems it would cause.
If you read the relevant thread you can see what a hit and miss affair doing this is.
Click to expand...
Click to collapse
Yeah, I tried the script myself on sale's rom and it just never worked. I could never boot back into the home screen. The odex me app at modaco worked a lot better than this script - for me anyway.
Sent from my GT-I9300 using Tapatalk 2
AW: [Q] Integrate Odex script into Aroma
Thanks to pardoned I was able to test the odex me app and it just Workshop fine!
Topic can be closed.
My question goes to ROM developer. If we can make a flash-able zip files to install or modify files, why can we not only flash the updated files when ROM developers update their ROM?
For example the normal process is:
-Find ROM your like
-Download and flash full ROM(some LG G2 Roms are 1 gig in size)
-New update comes out
-Download full 1 gig ROM again and flash again
why can we not go
-Find ROM
-Download and flash full ROM
-New update comes out
-Download only the updated files (most likely a few MB's only)
-Flash them
Note: I am not a ROM developer so I do not know all the technical aspects that goes into making a ROM. This is why I am asking why something like this is not possible or we just don't do it.
Some roms do support incremental updates. The G2 roms probably aren't that stable yet.
We're just now starting to see an more and more custom 4.4 roms (even on the Nexus 5). Most were typically based off stock.
Once they get stuff ironed out, you should start to see some smaller updates.
1gb roms do sound unnecessary
-sent from my LG G2 using XDA Premium 4
Thanks. I was really wondering about that. So it is possible, it is just up to the developer.
player911 said:
Some roms do support incremental updates. The G2 roms probably aren't that stable yet.
We're just now starting to see an more and more custom 4.4 roms (even on the Nexus 5). Most were typically based off stock.
Once they get stuff ironed out, you should start to see some smaller updates.
1gb roms do sound unnecessary
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
I may be really off base here. But from past phones and roms it seems that some updates only work really well when built into the Rom. Some have used SVN to put out updates and then you build the Rom with the small update you download. I believe it all depends on how deep the update goes. Looking forward to see how far we can go with this phone. Tomorrow is my 14th day so I guess its a keeper.
CyanDelta does what you are asking for Cyanogenmod.
Consider this. A developer creates a ROM. You download and install it. Then, the developer wants to update it. If he uses a small incremental update, you can download and flash it. Then when it is updated again, you just flash the next update, and so on.
This is all fine and dandy, if you downloaded the ROM from the very beginning, prior to any updates.
If you find the ROM a few weeks or a month or whatever into development, it will likely have gotten at least a few updates. But in order to get to the latest stuff, you would have to download that first build, flash that, and then individually download and flash every update that has been released for that ROM until it is up to date. That is a pain.
If the developer just releases a whole new build for each update, both new and old users can flash it and be on the most current version of the ROM. Yes, it is a bigger file to download, but it saves quite a lot of headaches. Both for the developer and for the end users. Especially if a re-flash is necessary for some reason.
Or, the developer could do both, and create a whole new build, and a small update for the current users. But that would make for a big mess of files to keep and maintain, and could be confusing to make sure the right one is downloaded. Just creating all those updates and ROM builds and writing all the installation scripts sounds like a big pain to me. It's generally simpler to just build the ROM. Still, it does happen.
Just my thoughts, and I am not a ROM developer, so please correct me if I am mistaken about something.
Its a pain plain and simple. Who wants to look at hases to see if a lib changed and stuff. Its also simply more reliable to just keep each base its own then to start merging the two.
Can anyone tell me why are there roms up of to 1gb in size and yet most are just 200mb more or less.
Usually AOSP ROMs are going to be small. When you start to add in LGs ui, features, provider rubbish etc, they climb in size. Most of my Galaxy Note II ROMs were huge. My TWRP back ups would be around 3GB.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Well thought I would pose the question as curious as to where to go next with our S2's
What are the advantages of the different versions of Android on the S2's and their sub versions??
What I mean by subversions is quite simple really 4.1.2 over say aosp 4.1.2?
We are on 4.1.2 Chameloen (me) 4.1.2 stock rooted(partner)
curios as to whether there's any point moving especially as kitkat onwards there no write to sd which is frigging STUPID!!!!
looking forward to your thoughts and opinions folks...
And thank you to all thoughs who take part..
regards
Lohtse
lohtse said:
Well thought I would pose the question as curious as to where to go next with our S2's
What are the advantages of the different versions of Android on the S2's and their sub versions??
What I mean by subversions is quite simple really 4.1.2 over say aosp 4.1.2?
We are on 4.1.2 Chameloen (me) 4.1.2 stock rooted(partner)
curios as to whether there's any point moving especially as kitkat onwards there no write to sd which is frigging STUPID!!!!
looking forward to your thoughts and opinions folks...
And thank you to all thoughs who take part..
regards
Lohtse
Click to expand...
Click to collapse
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
WardenBerret said:
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
Click to expand...
Click to collapse
Thank you for your reply very useful
but what are apps you have mentioned?
WardenBerret said:
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
Click to expand...
Click to collapse
What sd card bug you are talking about? Are you talking about the music bug? Because I've never heard or a problem where there was some problems with external sd card mounting.
lohtse said:
Thank you for your reply very useful
but what are apps you have mentioned?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix
I'm still on jellybean so i don't know even if it will show "This app is incompatible with all of your devices." if you have a kitkat rom, since its not official rom. Therefore the Xposed module is much more preferrable imo.
I can't offer any personal guarantees as whether it works or not.
gsstudios said:
What sd card bug you are talking about? Are you talking about the music bug? Because I've never heard or a problem where there was some problems with external sd card mounting.
Click to expand...
Click to collapse
The first kitkat builds had, for some strange reason, disallowed access to external sd cards, if any. Needless to say many people were not happy, and it wouldn't surprise me if the later builds removed this bug.
But if you have this bug, it basically means you can't use your external sdcard for anything unless you have root.
WardenBerret said:
https://play.google.com/store/apps/details?id=nextapp.sdfix
I'm still on jellybean so i don't know even if it will show "This app is incompatible with all of your devices." if you have a kitkat rom, since its not official rom. Therefore the Xposed module is much more preferrable imo.
I can't offer any personal guarantees as whether it works or not.
The first kitkat builds had, for some strange reason, disallowed access to external sd cards, if any. Needless to say many people were not happy, and it wouldn't surprise me if the later builds removed this bug.
But if you have this bug, it basically means you can't use your external sdcard for anything unless you have root.
Click to expand...
Click to collapse
thank you for the links... may give 5.0.2 or 4.4.x a try now....frigging stupid move not allowing write to sd etc in my opinion...... shame the community has to fix Googles screw ups!!
* I know the word "best" in the title is a crazy word to use.
If I can at least narrow down what to look for and where it is I'll have a good start.
There are so many guides for so many various ROMs, Lineages, apps, launchers, etc I am utterly lost.
I see one "Index" called "Verizon Galaxy Note 3 Android Development" which I suppose I ought to *ONLY* look at, but then I also see pages that tell me I can put Android Oreo or Nugget on my phone! How? Which one?
Is this so? Where are those ROMs and are they installed differently that the ones in the "Verizon Galaxy Note 3 Android Development" section? Must I only consider 4.4.2 ROMs? Aarrrgh!
When the phone starts up we see the Verizon logo and an unlocked lock that says Custom underneath. I can choose Continue or Recovery.
* Continue runs the stock phone.
* Recovery runs a safestrap 3.72 (twrp v2.7.0.0) window with 8 option buttons.
The phone is an SM-N900v 4.4.2 build nc4.
I see a lot of n9005 options. Should I consider those ROMs?
I understand the concept of downloading a ROM to a miniSD card and using safestrap to load from the SD card. Is it that simple or ???
Mostly because it was the 1st ROM I came across that I found a way to download, I downloaded:
[ROM ] [4.4.2] N9005XXUFNG2 v2 [07 AUG ] HaWKiSH ELITE SERIES [ 5 THEMES ] by zohawkish
Bad choice?
Can't I get something newer with newer features?
Please answer this cry for help from a very confused dude!
Thank you all so very much.
ElMudshark said:
* I know the word "best" in the title is a crazy word to use...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post/move this question within the Q&A Sub-Area of the following device specific area of the forum.
https://forum.xda-developers.com/galaxy-note-3
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.