1. I think it's really stupid forcing captcha before every post,
2. Stopping legitimate questions about a specific ROM from being posted directly on the specific ROMs thread until you have 10 post is also stupid,
3. I know it's pointless asking this question here SINCE THE DEV WILL NEVER SEE IT!!!!!!!, but have you ever considered incremental updates? The download site is slow and it seem pointless downloading the full ROM when only minor changes have been made.
mdhowes said:
1. I think it's really stupid forcing captcha before every post,
2. Stopping legitimate questions about a specific ROM from being posted directly on the specific ROMs thread until you have 10 post is also stupid,
3. I know it's pointless asking this question here SINCE THE DEV WILL NEVER SEE IT!!!!!!!, but have you ever considered incremental updates? The download site is slow and it seem pointless downloading the full ROM when only minor changes have been made.
Click to expand...
Click to collapse
I fully agree with Ypur first and second point.
Yeah, any idiot can get past a captcha.
There should be a test:
"you've flashed a ROM, but not the boot.img, should you:"
a) ask in the ROM thread why phone is broken
b) ask in Q&A section why phone bootloops
c) ask if flashing boot.img is required
d) tell everybody it's easier with Samsung
e) flash boot.img
I've been caught out by the 10 post restriction on the Developer threads, but usually found the answer after a quick search or just waiting a day or so to see if the same query gets raised.
As for incrementals, good idea for those that are coming from that base ROM, but not much for those that are flashing it for the first time.
Unless you want a new base ROM, and the incrementals? In which case poor Mr Dev does enough work already!
ARHD on my One X is working fine so far. I have the odd issue with not seeming to be able to connect over mobile data, but it is WAAAY less often than when it was stock. Pretty poor from HTC to release their flagship with so many radio based problems.
Meh. Mondays
Phew, glad I'm not alone with my frustration about captcha and post limits. Thought I might have seemed agro.
Incremental only on same base. Ie; 9.0.0 to 9.1.0. Seems silly downloading the whole 500mb for minor changes.
BenPope said:
Yeah, any idiot can get past a captcha.
There should be a test:
"you've flashed a ROM, but not the boot.img, should you:"
a) ask in the ROM thread why phone is broken
b) ask in Q&A section why phone bootloops
c) ask if flashing boot.img is required
d) tell everybody it's easier with Samsung
e) flash boot.img
Click to expand...
Click to collapse
Hahaha, made my night
Yeah, i also hated the unreadable Captcha o_0
Sent from my HTC One X / Desire HD using xda premium
Yep, just a pointless post to get my count up...
mattspew said:
1. I think it's really stupid forcing captcha before every post,
2. Stopping legitimate questions about a specific ROM from being posted directly on the specific ROMs thread until you have 10 post is also stupid,
3. I know it's pointless asking this question here SINCE THE DEV WILL NEVER SEE IT!!!!!!!, but have you ever considered incremental updates? The download site is slow and it seem pointless downloading the full ROM when only minor changes have been made.
Click to expand...
Click to collapse
I´ve got the "Point-2-Problem" too
Well, after reading nearly 300 sites in the ARHD Thread, i sometimes saw the same Questions by many Users with XXX Posts.
This let me doubt the 10-Post-Regulation, but i can also understand that the developers are herried about noob Spam...
Anyway... i think every noob can get a custom rom on a HOX by reading the Thread, just some Time is needed.
But it would be really nice when a newbie could also ask or share some experience, even on a brand new ROM like ARHD 9.1.0.
It is just to keep the thread clean is what I feel. Don't forget that everyone isn't a techie and might just post a dumb question upon registering.
BTW, I have never had to post a question since same is posted atleast once. If not, combining a couple of posts definitely answers my question :laugh:
Trust me, I am on 9.0.0 and it's worth waiting.
Related
Hi,
Today my Defy arrived
Now I have read many threads about the phone and the firmware, but soneones making me confused and other ones doesnt answer my questtions.
So, what I want to know is:
1. Wich is the really latest firmware for the Defy with the red lense? Done
2. when Im going to install CM7, must be flashed an stock froyo rom before? Done
3. because swype is preinstalled in the firmware, how can i update it to the latest version? Done
4. how can i make my own swype theme?
I think thats all (for now )
Greetings
I'll only answer to the ones that I know the answer...
2. The instructions say that you should. Also, from what I read, every tutorial says that you should go to stock. Also, a wipe could be advisable (not to inherit problems and bad settings from the previous ROM)
3. You can get it from the official site. As far as I've noticed CM7 doesn't come with Swype.
Hopefully someone else answers the other two questions.
Have a nice day!
And I'll take the opportunity to ask a few somewhat related noobie questions:
"the Defy with the red lens"
Click to expand...
Click to collapse
I've seen a few mentions of different lens colours. What is this? (link to explanation is fine) ETA: Found it myself. Really stupid to ask. Bottom line ATM seems to be that for phones recently manufactured the lens colour is not a reliable indicator of camera module used.
"every tutorial says that you should go to stock" (before flashing)
Click to expand...
Click to collapse
Doesn't this mean that you don't need to do anything special (maybe wipe everything, but maybe not that important?) when you flash a new ROM into the phone for the first time?
Or would you still need to first flash a plain stock ROM if your phone came with some telco-provided crappy stuff in the ROM, before flashing a custom ROM?
(Purely hypothetical question for me.)
Bumping this, because I am getting to closer to actually start rooting around (hah!) in the innards of my phone, and I keep wondering about this:
Aspsusa said:
Doesn't this mean that you don't need to do anything special (maybe wipe everything, but maybe not that important?) when you flash a new ROM into the phone for the first time?
Click to expand...
Click to collapse
So do I need to flash _another_ stock ROM before I switch to cyanogen or whatever, if my phone is a virgin that came with the stock nordic rom (moto_version.34.177.5.MB525.retail.en.ND/jorem_U3_3.4.2_177-5)?
It somehow seems redundant to me to flash another stock to my phone when I already have a stock froyo (without blur even) on it.
BTW, given the focus of this forum you are all being very very kind to us noobs. Upthread I asked a really really really stupid question (I'll see if I can edit out), and nobody threw rocks at me .
I am still wondering though whether anyone can recommend an alternative forum more suited to Really Basic Questions?
Just root, install second init for recovery, then flash cyanogen...
If you click devices at their website, you can grab the latest nightly ROM, and you will also find the wiki, which has a step by step on how to do everything.
It's really simple, just keep glued too the instructions.
Good luck
Aspsusa said:
Bumping this, because I am getting to closer to actually start rooting around (hah!) in the innards of my phone, and I keep wondering about this:
So do I need to flash _another_ stock ROM before I switch to cyanogen or whatever, if my phone is a virgin that came with the stock nordic rom (moto_version.34.177.5.MB525.retail.en.ND/jorem_U3_3.4.2_177-5)?
It somehow seems redundant to me to flash another stock to my phone when I already have a stock froyo (without blur even) on it.
BTW, given the focus of this forum you are all being very very kind to us noobs. Upthread I asked a really really really stupid question (I'll see if I can edit out), and nobody threw rocks at me .
I am still wondering though whether anyone can recommend an alternative forum more suited to Really Basic Questions?
Click to expand...
Click to collapse
It is recommended as a precaution for a failsafe install but you can install CM7 on any stock 2.2 or above rom.
Sent from my MB525 using Tapatalk
ryan8r said:
It is recommended as a precaution for a failsafe install but you can install CM7 on any stock 2.2 or above rom.
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
Took the words right out of my mind...
Sometimes I skip right past the important stuff. Lol
hi,
Everythinbg excepted 4. is solved by my own.
For now i just need to know hox to make my own Swypw skin.
BTW: I hate Threadhooligans
MrGentlemen said:
BTW: I hate Threadhooligans
Click to expand...
Click to collapse
Mean me? Wanna fight?
BTW, it would be good if you'd change the topic back, or put the old topic in parenthesis to the new one or something. Something like
[request]Swype-skinning ([solved]stock froyo first & red lens latest)
might be good
I was wondering why I was subscribed to a thread about swype-skinning, as it couldn't be further from my interests, but never mind that - there's good info in this thread not related to swype.
Aspsusa said:
BTW, it would be good if you'd change the topic back, or put the old topic in parenthesis to the new one or something. Something like
[request]Swype-skinning ([solved]stock froyo first & red lens latest)
might be good
I was wondering why I was subscribed to a thread about swype-skinning, .
Click to expand...
Click to collapse
Exactly. I was confused, and for an instant, lost in space.. Lol
You big thread hooligan, Mr gentleman
Edit:
To answer your question,
You should probably check with Swype to see if skinning is even capable with their app... (or potentially even allowed)
To my knowledge, skinning Swype is uncharted territory...the app is in beta still.
Some advanced knowledge of Android would be required to hack, disassemble, and recompile any themes for it.
[Q&A] [ROOT] [ROM] [LP] [5.0.1] Stock ROOTED Lollipop for Retail Edition [N910VVRU1B
Q&A for [ROOT] [ROM] [LP] [5.0.1] Stock ROOTED Lollipop for Retail Edition [N910VVRU1BOAF]
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 [ROOT] [ROM] [LP] [5.0.1] Stock ROOTED Lollipop for Retail Edition [N910VVRU1BOAF]. 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!
What has this method been tested on?
ODSTZ3RO said:
What has this method been tested on?
Click to expand...
Click to collapse
You seem to be all over the place asking this same question, I'll answer it with the answer I got just by reading the threads that you've posted this question on.
1. He is testing it on the Verizon Note 4 (Non-Dev Edition) FIRST
2. Once its successful ( which it isn't as of this post) he will Attempt to make it work For you AT&T Note 4 Users.
I'm sorry if this seems rude, but you've literally asked this 5 times to my knowledge and I've only been aware of this ROM being developed for 30 minutes as of this post, and I was able to answer your question.
hsbadr said:
IMPORTANT INFORMATION: THE METHOD USED IN THIS THREAD IS SUCCESSFUL ON UNROOTED DEVELOPER EDITION WITHOUT USING A RECOVERY OR AUTOROOT. FOR RETAIL EDITION, IT IS NOT A KINGROOT ISSUE AT ALL. THE LOCKED BOOTLOADER SENDS A FLAG TO UFS CONTROLLER TO WRITE PROTECT PARTITIONS INCLUDING SYSTEM. I AND @gatesjunior ARE INVESTIGATING A WORKAROUND TO REMOVE WRITE PROTECTION.
THIS MAY TAKE A LONG TIME AND IS NOT GUARANTEED !
Click to expand...
Click to collapse
@hsbadr has been very busy trying to get this work for us, I know that you're excited, but please have some more patience.
toxict33n said:
You seem to be all over the place asking this same question, I'll answer it with the answer I got just by reading the threads that you've posted this question on.
1. He is testing it on the Verizon Note 4 (Non-Dev Edition) FIRST
2. Once its successful ( which it isn't as of this post) he will Attempt to make it work For you AT&T Note 4 Users.
I'm sorry if this seems rude, but you've literally asked this 5 times to my knowledge and I've only been aware of this ROM being developed for 30 minutes as of this post, and I was able to answer your question.
@hsbadr has been very busy trying to get this work for us, I know that you're excited, but please have some more patience.
Click to expand...
Click to collapse
I've only referred to this twice one in here and the other in the root progress thread. Also his initial post about this was sent 19 h ago ,I was kind of hoping he'd have all of this sorted out before posting anything. I'm glad he didnt give up like others did ,but even the Dev root thread was closed due to his post and other reasons. Thanks for answering though I actually wanted to know if anyone else was daring enough to test this on their own behalf using the at&t model ,I wasn't referring to him directly. I guess asking the simplest of questions annoys people very quickly ,I'll make sure to be specific and only post once next time.
ODSTZ3RO said:
I've only referred to this twice one in here and the other in the root progress thread. Also his initial post about this was sent 19 h ago ,I was kind of hoping he'd have all of this sorted out before posting anything. I'm glad he didnt give up like others did ,but even the Dev root thread was closed due to his post and other reasons. Thanks for answering though I actually wanted to know if anyone else was daring enough to test this on their own behalf using the at&t model ,I wasn't referring to him directly. I guess asking the simplest of questions annoys people very quickly ,I'll make sure to be specific and only post once next time.
Click to expand...
Click to collapse
Yeah, no hard feelings, next time more info would be better. Don't ever be afraid of writing a long post, If anyone comes to XDA, they know that the more INFO the better they can help you.
do you think he will be able to get the final touches on this method?
I've been following this thread since I first bought my note 4 in December I never posted because I don't have anything informative but I'm very phyced never had a device longer then a week without root; do you guys actually think root will be fully accomplished it seems like we keep hitting roadblock after roadblock? And what's up with this king root v4.0 who developed this and was it actually made for the note t or does it just happen to kind of work for vzw note ?
Flyin350z said:
I've been following this thread since I first bought my note 4 in December I never posted because I don't have anything informative but I'm very phyced never had a device longer then a week without root; do you guys actually think root will be fully accomplished it seems like we keep hitting roadblock after roadblock? And what's up with this king root v4.0 who developed this and was it actually made for the note t or does it just happen to kind of work for vzw note ?
Click to expand...
Click to collapse
Kingroot works for various devices and happened to give temporary root for the note 4. That added a huge filling of the root progress bar for the note 4. Temporary root can lead to good things. These devs work hard and I am sure it will be root-able soon. As for an ETA, "It'll happen when it happens". I'm being positive about it.
I was gong to mention this earlier. Hopefully temp root could assist in removing security from the boot loader, from what I've read the boot loader is what is preventing full root. This would also allow us recovery and ability to flash roms/kernels hopefully unlocking the bootloader is easier now!
m0j0j0j0 said:
I was gong to mention this earlier. Hopefully temp root could assist in removing security from the boot loader, from what I've read the boot loader is what is preventing full root. This would also allow us recovery and ability to flash roms/kernels hopefully unlocking the bootloader is easier now!
Click to expand...
Click to collapse
I wish it were that simple. Sadly, I don't think we will ever have a bootloader unlock. I am sure that we will have root, though. I am fine with just root. XDA devs have worked like crazy to get it and they are so very close.
Patience is the key to success trust me.....
should I do this method
I'm not 100 percent sure should I not do this method yet I don't mind testing it but will I achieve root If done correctly on my Verizon note 4
Flyin350z said:
I'm not 100 percent sure should I not do this method yet I don't mind testing it but will I achieve root If done correctly on my Verizon note 4
Click to expand...
Click to collapse
Temp root only on retail edition. Bootloader fsends a flag to kernel and it write protects cetrain partitions including system, the way I read it. And THAT (write protection) is keeping us from full root because we cant write superuser to system partition
(im dumb and may not have pieced it all together right, but thats how I understand it)
YouTube video kingroot??
Theres a video on youtube posted a few hrs ago by droidmodderx the same guy whp did the april fools joke with note 4 root method: he is claiming the kingroot qorks for note 4 on lollipop with no issues and even roots it on camera with his verizon note 4, i cant tell though if he's running lollipop but it Def is a Verizon note 4; I can't post links cuz I'm a newbie the funny think is I've been using XDA for 2 years just never posted I'm sure if you search YouTube for Verizon note 4 root and change the search options for videos in last week it will pop up from Droidmodderx Root
A DevEd Note4 can be done, Retail can not because of the write protection... Unless you can see if its dev or retail I wouldnt buy into the hype. Read what our devs here are saying about it in the root rom and multisystem threads
Comments on video are filled with people saying it doesnt work and that root is lost on reboot, and that this causes random reboots...
lexbian said:
A DevEd Note4 can be done, Retail can not because of the write protection... Unless you can see if its dev or retail I wouldnt buy into the hype. Read what our devs here are saying about it in the root rom and multisystem threads
Comments on video are filled with people saying it doesnt work and that root is lost on reboot, and that this causes random reboots...
Click to expand...
Click to collapse
What video ? On lolipop ?
Sent from my SM-N910V using Tapatalk
Yes, the video mentioned in OP... this one. You see no real info about the phone other than the word verizon on the backplate, and the fact that he ran Kingroot and Root Checker. But the comments are a mixed bag of claims. Lots say it doesnt work or stops halfway, or causes random reboots..
https://www.youtube.com/watch?v=QicDqTKb_sU
lexbian said:
Yes, the video mentioned in OP... this one. You see no real info about the phone other than the word verizon on the backplate, and the fact that he ran Kingroot and Root Checker. But the comments are a mixed bag of claims. Lots say it doesnt work or stops halfway, or causes random reboots..
https://www.youtube.com/watch?v=QicDqTKb_sU
Click to expand...
Click to collapse
Oh this video yea I saw this one. I thought that was from the LP thread here.
I see the instructions however I would prefer seeing video so I don't screw anything up
@hsbadr has said to wait for final instructions and the accompanying video. Im twitchy... I wanna try it anyways, but I dont fancy the idea of a (possibly) compromised device. Ill wait til we get fixed up with the prerooted rom and multisystem. Hell... I've waited this long already. Ive almost forgotten what i wanted root for with some of the non-root replacements Ive found.
lexbian said:
@hsbadr has said to wait for final instructions and the accompanying video. Im twitchy... I wanna try it anyways, but I dont fancy the idea of a (possibly) compromised device. Ill wait til we get fixed up with the prerooted rom and multisystem. Hell... I've waited this long already. Ive almost forgotten what i wanted root for with some of the non-root replacements Ive found.
Click to expand...
Click to collapse
The instructions have been already updated (works perfectly on unrooted Developer Edition), but Samsung implements write protection on the system partition for Retail Edition only (tripped by the locked bootloader) & so, all our changes get lost after a reboot (even if you deleted directories in /system, they'll come back after rebooting the device). We're working on a workaround...
lexbian said:
@hsbadr has said to wait for final instructions and the accompanying video. Im twitchy... I wanna try it anyways, but I dont fancy the idea of a (possibly) compromised device. Ill wait til we get fixed up with the prerooted rom and multisystem. Hell... I've waited this long already. Ive almost forgotten what i wanted root for with some of the non-root replacements Ive found.
Click to expand...
Click to collapse
Same never went this long without it. Lollipop got me a little further but I'm already getting twitchy
Verizon Wireless Technician and Samsung Galaxy Note Series Owner
Keep the trouble shooting questions for each specific ROM or Kernel to THEIR threads. So that way Devs can be made aware of any errors to be able to work on, if need be, and for when people are searching for solutions to their problems the answers won't be scattered around. Consolidation makes everything easier!
What's your build? What are you loving about it? Any MOD recommendations?
Mine:
Viper10 ROM by TeamVenom
ElementalX Kernel
&
A.R.I.S.E
Sound Systems™ audio MOD
I'm a first time rooter (introduced to it by my fiance) and aspiring developer. I am going back to school to get that ball rolling. I'm socially awkward whilst being a social butterfly (once I'm out of my shell). The A.R.I.S.E team and TeamVenom have helped me to come out of that shell here on XDA so I'm ready to get socializing and talk all things root! However, I don't want to blow up their threads with unrelated posts...and so I've created this thread - so let's have at it and share ideas, opinions, and have fun! Remember to keep issue/ questions related to each ROM, Kernel, MOD etc. posted ON THEIR threads! So please include a link to their XDA thread when sharing what you've got.
Be kind and respectful. And have fun!
(Still need assistance with getting your HTC 10 rooted? Check This Guide out!)
https://youtu.be/1iAYhQsQhSY
Mine are
LeeDrOiD10 ROM
either with the build-in
~clumsy~ Kernel
or
ElementalX Kernel
No sound mods as the audio boost of LeeDrOiD is workin' just fine with the build in DACs
Used Viper for a long time and it is a great ROM. In fact I went to LeeDrOiD10 cause the tweaks on Viper10 are just so many, and most of them I've never used at all. On LeeDrOiD there are just a few tweaks, where all those I need and use are present.
Cheers
Only Cool Kids Reply to Their Empty Threads
EDIT: Lol got a post while taking 10 years to write this one...so it doesn't appear as though I was my own first response...but if I wrote like a normal person, I would have been.
TL;DR - Zip below will get rid of red message during boot, REQUIRES S/OFF, if you choose to flash this I'm NOT responsible for bricked phones, this zip file works for US Unlocked HTC 10 phones - but I'll rewrite the files inside to match your CID if you need me to, not originally my work and I don't know who's it is...sorry!
-Rename the zip file 2PS6IMG.zip & place it in the external SD card
-Boot down to download mode and if it's all groovy there will be a message at the bottom outlining that it found the "2PS6IMG" zip file and will tell you to press VolUp to proceed with the flash or VolDwn to continue to the normal download mode screen options
NOTE: if your screen doesn't display that initial message at the bottom and just goes to the normal download mode options then you've named the zip file wrong. Make sure that you didn't end up with 2PS6IMG.zip.zip during the renaming process - it HAS to read 2PS6IMG.zip or download mode will not see it as it is scanning for that name exclusively!
- If you got the message go ahead and hit volume up and, when prompted at the end, hit the power button. If you're phone boots down immediately after hitting the volume up button DON'T FREAK and leave it be. It'll kick back up and finish it's thing.
- Reboot and enjoy! (First boot up may take longer than you're comfortable with, that's normal chill for a moment and it'll all work out)
(First to reply to my own thread, crazy stuff happening here...watch out! )
Never understood why the TL;DR is put at the bottom. I know I write novels...I love words but I feel the TL;DR is more thoughtful to place at the top...so you don't have to wade through the overwhelmingly copious amounts of my words to find out there was a TL;DR option. Always thinking of you :angel: however, surely there exists an individual who not only continues and reads my posts in their entirety, but is as entertained reading it as I am writing it!
.............
Anyway, since this is meant to be a thread in which we share fun rooting tweaks and whatnot, I thought I'd go ahead and add this zip file. If you aren't a fan of the red message during the boot up that appears after you've successfully rooted - I've got your solution! I do have to apologize... I'm not sure who the original creator is. My fiance sent the file to me through Bluetooth and I rewrote a couple lines in the file so it would work with my CID. I tried to find the correct individual or thread to link in order to give them the proper credit, but there were a few posts for it so I'm unsure who it is. Just know I'm not trying to claim this for my own... just sharing the love :victory:
MAKE SURE YOU ARE S/OFF BEFORE DOING THIS! YOU'RE FLASHING THIS ON YOUR OWN ACCORD, I'M NOT RESPONSIBLE FOR ANY SOFTWARE/ HARDWARE FAILINGS
This is for the US Unlocked phones. So if you're not US Unlocked, but you want up in this sexy zip action, let me know and I can rewrite the file for you. The CID just needs to be rewritten to match the one on your phone. As a precaution I also rewrote the "mainver" line. It had the original 1.21.531.1 (T-Mobile's current software number) to the updated 1.80.617.1 (the current software number for US Unlocked). I wanted it all lined up perfectly, just in case, however IDK if you need to rewrite the "mainver" live in that text file my phone is fully functional after the rewrite and flash so I'm confident that I took the right steps. I posted what I've got going on for my custom ROM/ Kernel in the OP, if that's important for you to know. I've got the instructions above in TL;DR - no need to repeat. Let me know if you have any questions!
:highfive:
5m4r7ph0n36uru said:
Mine are
LeeDrOiD10 ROM
either with the build-in
~clumsy~ Kernel
or
ElementalX Kernel
No sound mods as the audio boost of LeeDrOiD is workin' just fine with the build in DACs
Used Viper for a long time and it is a great ROM. In fact I went to LeeDrOiD10 cause the tweaks on Viper10 are just so many, and most of them I've never used at all. On LeeDrOiD there are just a few tweaks, where all those I need and use are present.
Cheers
Click to expand...
Click to collapse
Thank you for the reply! I haven't checked LeeDrOiD10 out personally, but I saw it on my fiances phone when he got uber frustrated at a camera defect post viper update. The V10 ROM update caused our kernel to be temporarily incompatible...so he temporarily ditched V10 and tried LeeDrOiD10.
He was saying the same things as you in regards to fewer customisation's. And hebmade mention of it being a little more user friendly. But, ultimately, he returned to V10
EDIT:@5m4r7ph0n36uru what exactly does the LeeDrOiD10 ROM offer in terms of the sound boost? An equalizer? Or a little more than that. I didn't check that feature out. I didn't know it was one. My other half may have known though. We love the crazy amounts of tweaking you can do with Viper4Android in the A.R.I.S.E. MOD and all their tweak.prop files/ profiles that we can load up!
Being a spectator of LeeDrOiD10 was sufficient enough for me...only because I know myself, and I LOVE having as many options and open doors, in regards to messing around with my phone, as possible. Tis more dangerous waters to tread that way...but that's all the fun! And I'm confident enough in myself to be able to recover from most things. After all XDA has strong support to offer!
Yeah I know and it always has been fun changing nearly every detail in a ROMs behavior as it is possible on Viper10. But in fact I guess I'm maturing from this phase in my live where modding was the one and only, as we'd say in germany.
In fact I'm getting older and less fascinated by all those features. Maybe it'll come a time when I'll again become fascinated by modding and tuning every tiny bit of a ROM, but at the moment I really just need some basics.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
Yeah I know and it always has been fun changing nearly every detail in a ROMs behavior as it is possible on Viper10. But in fact I guess I'm maturing from this phase in my live where modding was the one and only, as we'd say in germany.
In fact I'm getting older and less fascinated by all those features. Maybe it'll come a time when I'll again become fascinated by modding and tuning every tiny bit of a ROM, but at the moment I really just need some basics.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
There's a flavor for everyone! And our taste buds change over time for sure. So long as you're happy with your phone and its features, that's all that matters!
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
really ...anyone who gets a brick because of not reading a thread certainly shouldnt be xda or even messing around with the phone in the first place. just stay stock if you wont read
We survived finely when Nougat was still new, so what makes Oreo special?
There's simply no good point to making a whole section for a particular version of Android. The same thing can be done simply with a proper thread title.
The problem isn't purely on the lack of separation of sections — It's the 5 seconds attention span that most seems to have because they can't read the first post of the thread they're in or they're too busy looking at butterflies and they ended up destroying their device and/or data inside the device.
I know we can't fix people, but that doesn't make for a good argument for creating a new section.
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
As stated. This is not gonna happen. If you cant do the proper research needed for what you are doing then you shouldnt be doing it in the first place.
I disagree with OP - there shouldn't be separate section for Oreo stuff. Ask yourself - what would happen, if released mod would be compatible with Marshmallow, Nougat and Oreo?
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
charackthe said:
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
Click to expand...
Click to collapse
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
zelendel said:
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
Click to expand...
Click to collapse
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
charackthe said:
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
Click to expand...
Click to collapse
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
zelendel said:
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
Click to expand...
Click to collapse
I see you all over the place! You are retired? You post on here like its full time lol
ZVNexus said:
I see you all over the place! You are retired? You post on here like its full time lol
Click to expand...
Click to collapse
I am a retired mod. My job allows for me to always be lurking around. Every couple of hours or so I check my email and catch up.
Been that way for as long as I can remember. Heck I used to be on far more in the early years.
We finally have PE treble thanks tobthe devs.
My main concern is regarding the stock kernel with new treble update. All i want to know is the best setup for the new PE rom. I am on non treble version and here i am using PE+heliox+boostv7+ubercool and the performance is unbeatable.
So i was thinking what will be the best setup for the latest treble update..?
I've tried treble kernels but kronic is still best. Wait for next update, i hope many problems would get fixed.
#3
Failed to update vendor image
Rahil4321 said:
I've tried treble kernels but kronic is still best. Wait for next update, i hope many problems would get fixed.
Click to expand...
Click to collapse
The battery backup is very poor and the phone gets heat up a lot and all game are lagging.
What about ar beast??
rince4 said:
Failed to update vendor image
Click to expand...
Click to collapse
First flash -Factory to vendor zip
Then flash treble twrp
And finally flash the rom.
Shouldn't this question be asked in the PE thread it self?
Anyways, just for information, I too have this same question. Myself a big fan of the old PE, indeed it has given me the best performance so far.
Presently waiting on AiCP 13.1 and I am following the PE thread to note down who is suggesting what and known good setups.
I guess reading the thread is better idea rather expecting everyone to contribute in a seperate section. Many may not simply come to see this thread or take the extra hassle to pen down twice !!
NaXal said:
Shouldn't this question be asked in the PE thread it self?
Anyways, just for information, I too have this same question. Myself a big fan of the old PE, indeed it has given me the best performance so far.
Presently waiting on AiCP 13.1 and I am following the PE thread to note down who is suggesting what and known good setups.
I guess reading the thread is better idea rather expecting everyone to contribute in a seperate section. Many may not simply come to see this thread or take the extra hassle to pen down twice !!
Click to expand...
Click to collapse
No one is sharing the best setup. Everyone is asking about their problems in the thread. So i made a different thread itself.
gunavat said:
No one is sharing the best setup. Everyone is asking about their problems in the thread. So i made a different thread itself.
Click to expand...
Click to collapse
I wonder if that means no one has found a satisfactory setup yet.
At least I concluded that and stayed on AiCP for the time being till all the answers about these common questions and solutions for those problems are found.
NaXal said:
I wonder if that means no one has found a satisfactory setup yet.
At least I concluded that and stayed on AiCP for the time being till all the answers about these common questions and solutions for those problems are found.
Click to expand...
Click to collapse
Maybe yes. Let's wait and watch
Anything??