Database Develop

[Q] "Brainstorming" SLCD support.

Dear developers,
i hope it is not too offensive, if so it's not my intention, but is there a way to make all your great ROMs compatible for nexus one SLCD!
Maybe you can share in this thread and it will make the development of compatible ROMs easier for you.
Many people would be happy about it.
Having a compatible recovery with RA RECOVYER 1.8.0.1 is more than just the first step.
Unfortunately I can not help you much, because i'm just consumer and no dev.
The issue is that after flashing several ROMs on SLCD the screen after the first splash screen stays black.
CM 6.0.0 is working after changing the update script before flashing.
I want to enjoy the great variety of your ROMs on my nexus one, so please try to help.
Thank you very much for your great work....!

I would just like straight answers.
Does SLCD support just require updated drivers?
Aren't the drivers included on AOSP?
And therefore, any ROM that draws straight from AOSP has the correct drivers?
Is it easier to install a custom ROM that supports SLCD if you have unlocked your bootloader?
Why is amon_RA 1.8.0.1 the only one that supports SLCD?
Why isn't 1.8.0.1 the most recent version available in the amon_RA recovery thread? And not the most current one listed in ROM manager?

You sound like someone owes you something. Which isn't the case.
Yes, updated drivers. Residing with the kernel, meaning updated kernel.
Yes, included in AOSP. Different tag/branch.
Which means - code needs to be imported/switches set/something else done. Not 1-minute job.
Bootloader doesn't matter. Not easier, not harder - just the same. It's done through recovery anyway.
Because Amon_Ra bothered to make one that supports SLCD.
Because there is a separate thread for it, and if you'd bother looking at the Nexus Wiki in Recovery section - you'd find it there, together with the note to flash it for SLCD. ROM Manager doesn't support SLCD, and in fact most, if not all, cases of "I flashed something and now I have a black screen" as of lately come from those that use ROM Manager. Why doesn't it support? Because it wasn't updated to support. Good reason not to use it and do things manually, at least until it starts supporting SLCD.
CM6 has SLCD support, Enomther is working on adding it, the rest of the devs are probably working on it too.

Jack_R1 said:
You sound like someone owes you something. Which isn't the case.
Yes, updated drivers. Residing with the kernel, meaning updated kernel.
Yes, included in AOSP. Different tag/branch.
Which means - code needs to be imported/switches set/something else done. Not 1-minute job.
Bootloader doesn't matter. Not easier, not harder - just the same. It's done through recovery anyway.
Because Amon_Ra bothered to make one that supports SLCD.
Because there is a separate thread for it, and if you'd bother looking at the Nexus Wiki in Recovery section - you'd find it there, together with the note to flash it for SLCD. ROM Manager doesn't support SLCD, and in fact most, if not all, cases of "I flashed something and now I have a black screen" as of lately come from those that use ROM Manager. Why doesn't it support? Because it wasn't updated to support. Good reason not to use it and do things manually, at least until it starts supporting SLCD.
CM6 has SLCD support, Enomther is working on adding it, the rest of the devs are probably working on it too.
Click to expand...
Click to collapse
Do you know which branch in the AOSP includes support for Nexus One SLCD?
I've already tried the froyo branch without any success and android-2.2_r1.1 branch crashes while flashing.

Didn't check the commits since looking for a way to change MMS resolution (and didn't look beyond that ), so I'm sorry, but I'm not the person qualified to answer. Asking someone from CM team or Enomther might be a better idea to find the Google source (since those ROMs have incorporated the support).
Enomther is basing on r1.1, so it should be usable. Never tried to compile myself, so I can't be of help there....
CM has this commit in his github (from pershoot's log):
87f604b7d75e77af62a2074e993a91aa00f1fcf5 ([ARM] mahimahi: add support for Sony TFT panel)
These are 4 repositories that might also hold the commit:
http://htc-linux.org/wiki/index.php?title=Kernel#Qualcomm_QSD8xxxx

Official custom rom support for i9295? Porting/ Patching from 9505 to 9295?

Hello Active-Users,
i think this might have been discussed earlier but i didnt find any specific thread about it.
In general i am really happy with my s4 active (international version). but the custom rom support is actually really poor. There are Ports for AOSP 4.2.2 and CM10.2, but i wonder, if and when we will get any "official" AOSP or CM-Support? Most of the Hardware is known because auf the s4 (9505) and it has official support because auf the "google edition". Differences are 1) Camera 2) Screen and two sensors, that are not there in the active. so for me (i am no developer at all!) it should be possible, to patch official s4 roms for our s4 active. but who has knowledge about these thinks? could we ask for support of some good developers, maybe do some donations or something like that...
its so sad to see the s4 community having tons of roms to try and we didnt have any official support.
so, what must happen for an official aosp/cm-support?
Thank you for answers,
greetings, moviecut

As far as I know, that's 2 stated differences between I9505 and I9295: 2 physical buttons and camera, not sure about other internal parts. Waiting for months for a good developer to have some minor tricks so that all I9505 is portable to I9295.

gtchuah said:
As far as I know, that's 2 stated differences between I9505 and I9295: 2 physical buttons and camera, not sure about other internal parts. Waiting for months for a good developer to have some minor tricks so that all I9505 is portable to I9295.
Click to expand...
Click to collapse
Since nobody has responded to this, I guess I will. To answer your question, yes you can more or less easily flash regular S4 ROMs onto our phones. Be aware that this has only been done in SafeStrap thus far. You could possibly make your phone unusable if you flash S4 ROMs as your only ROM without using SafeStrap.
To use a regular S4 ROM in SafeStrap:
Flash your desired regular S4 ROM into a new slot in SafeStrap. Currently you can only fash 4.2.2 TouchWiz based ROMs due to a kernel limitation with SafeStrap. I believe @Hashcode is still working on this and hopefully we will eventually be able to use any kernels with SafeStrap.
Without rebooting, flash the MOD file of your stock ROM. So if your stock ROM is MF1, then flash the MF1 MOD file. MF2....flash MF2 MOD file, and MF3...flash MF3 MOD file. The MOD files can be found here.
Again without rebooting, flash the camera fix that was put together by LeJay. The camera fix can be found here.
Make your new ROM slot the active ROM slot and reboot your phone.
Once in the new ROM you need the key layout file in order to use the hard menu and back keys that the Active has. Go into /system/usr/keylayout using a file explorer, and add:
key 139 MENU
key 158 BACK
to gpio-keys.kl with a text editor. after that, reboot and they work like they should. (thanks to @hokeymcf for posting these instructions)
If any of this information is wrong please let me know and I will update this post so people don't brick phones. Please note that this has only been reported to work in SafeStrap so far, flashing regular S4 ROMs as your stock ROM could brick your device and has not been tested yet.

Devo7v said:
Since nobody has responded to this, I guess I will. To answer your question, yes you can more or less easily flash regular S4 ROMs onto our phones. Be aware that this has only been done in SafeStrap thus far. You could possibly make your phone unusable if you flash S4 ROMs as your only ROM without using SafeStrap.
Click to expand...
Click to collapse
Safestrap is only for the i537 - the AT&T S4 Active - this thread is about the i9295 which doesn't according to the safestrap post have that option. Flashing the roms directly won't work simply because without safestrap we run into the kernel issue of not having the right display drivers, and so the phone just won't work.

[Q] Network problems (RIL) with latest Beanstalk 4.4

Hi,
I installed 2 weeks ago the latest Beanstalk 4.4.4010 CM-based and I really liked it, it is a very nice ROM and increased the life and performance of my phone by a lot.
At the beginning everything was fine, but now after 2 weeks I am having again the same network problems (losing connectivity, not being able to recover signal, and so on) that I had with my old CM ROM.
After reading a bit around in the forum, I found that there is this RIL change solution http://forum.xda-developers.com/showthread.php?t=2496075
But since this is a bit older, I don't know if it has been already implemented or not in the recent Beanstalk updates or if I still have to do it. And also if this only works with the P880-dev based ROMs or also with the CM based ones. It is difficult to say when one has to read so many threads.
Also an user uploaded a flashable zip fix of the RIL for the AD version. Does this mean that I can flash the P880-dev based ROM with AD and then just flash this zip and would avoid having to do the procedure of the above tutorial?
Is there another flashable alternative for me?
I also read somewhere that NamelessRom wasn't having this issue, so do you recommend to switch?
Thanks,
SC.

there are still several versions of RIL; i recommend you try a few of them till you find out the one that works.
the zip that was made for the AD version of rom works only and only with that specific rom, made on that specific date. any rom that was built after (or before) needs to have different flashable zip.
i do recommend you try nameless rom first (take a backup of beanstalk). take it for a spin for a few hours/days and see if you have any network issues. if you do not, you can extract RIL from nameless rom & implement it in beanstalk. good luck

Flying_Bear said:
there are still several versions of RIL; i recommend you try a few of them till you find out the one that works.
i do recommend you try nameless rom first (take a backup of beanstalk). take it for a spin for a few hours/days and see if you have any network issues. if you do not, you can extract RIL from nameless rom & implement it in beanstalk. good luck
Click to expand...
Click to collapse
:good:
Thanks, then I'll try my luck with Nameless. I hope I will not miss it much.
There isn't yet something like dual booting in Android, no?
Cheers,
S

There is for our device, search for twrp multirom. Its a bit of a hassle to set up properly thoguh

[Q] New guy looking for some good guidance

Ok so I got into this because I got a spare phone from a guy that tried to root and install custom rom but couldn't get it to work and had thought he had bricked the phone. The phone still worked but would not display anything so I used adb and installed multirom recovery and then flashed I believe the fluent lollipop rom. got the screen to work and added a secondary bad boyz rom to install. What I want to do is find a good beginners guide on what a Kernel is and what to look for when changing roms and kernels, would like to try CM12 lollipop so would need to know which recovery to install and how to uninstall the multirom, and would like to just find a straight forward breakdown of how this works. thanks again for any teaching I can gain from anybody.

Jayare_H said:
Ok so I got into this because I got a spare phone from a guy that tried to root and install custom rom but couldn't get it to work and had thought he had bricked the phone. The phone still worked but would not display anything so I used adb and installed multirom recovery and then flashed I believe the fluent lollipop rom. got the screen to work and added a secondary bad boyz rom to install. What I want to do is find a good beginners guide on what a Kernel is and what to look for when changing roms and kernels, would like to try CM12 lollipop so would need to know which recovery to install and how to uninstall the multirom, and would like to just find a straight forward breakdown of how this works. thanks again for any teaching I can gain from anybody.
Click to expand...
Click to collapse
Start Here.
http://forum.xda-developers.com/showthread.php?t=2700666

Hulkanator said:
Start Here.
http://forum.xda-developers.com/showthread.php?t=2700666
Click to expand...
Click to collapse
Thank you that was a very good read.

For information on MultiROM (and how to remove it) check the thread below:
http://forum.xda-developers.com/htc-one-m8/development/multirom-v28-unofficial-port-t2884413
For an explanation of what the kernel does, look below:
http://m.androidcentral.com/android-z-what-kernel
As far as recoveries go, your best bet is to stick with TWRP. You can find links to the official version in the TWRP thread in Original Development. Captain Throwback also maintains an "unofficial" version offering MultiROM support over at theMikMik.

Any good dual boot solutions out there?

I've checked multiROM Manager and XT1254 is not supported, however if some dev would like to take a crack at it here is a wiki that explains how to port it (and if you can in the first place). I've also done extensive testing with dual boot patcher. I got it to work once with a 4.4 ROM (I can't remember exactly which), but after switching back and forth between the ROMS once I couldn't "escape" the secondary ROM and had to restore a backup to get back into the primary ROM (crdroid v3.3).
If you have attempted to dual boot on the Droid Turbo please leave your experiences and findings below, I'd love to see a working solution. Thanks!
Edit: I've found two that work with crdroid v3.3
Bliss xda post Specific tested ROM download
AOKP version list (there is no marshmallow xda post) Specific tested ROM download

Well I have found one ROM (AOKP MM unofficial) that worked flawlessly with dual boot patcher running on crdroid v3.3. What's odd is that the nougat version by the same author does not work, and in fact no nougat ROM has worked with dual boot patcher for me.

Just some commentary... I've never understood the multi-ROM booting thing. I really only run one ROM at a time for both me and my wife. (I buy two phones at a time, and keep them identical as far as settings.) I do have many more apps than my wife -- but same phone, same ROM, same settings.
If I wish to save a ROM to try another out, I can always use TWRP backup save my current ROM and settings, and temporarily install another to see if it's better. But I have no desire to constantly switch back and forth between ROMs, for my "daily driver".
I'm not criticizing your desire in any way, I'm just suggesting maybe that's why it's not available with this phone. Not much demand for reasons I stated.

ChazzMatt said:
Just some commentary... I've never understood the multi-ROM booting thing. I really only run one ROM at a time for both me and my wife. (I buy two phones at a time, and keep them identical as far as settings.) I do have many more apps than my wife -- but same phone, same ROM, same settings.
If I wish to save a ROM to try another out, I can always use TWRP backup save my current ROM and settings, and temporarily install another to see if it's better. But I have no desire to constantly switch back and forth between ROMs, for my "daily driver".
I'm not criticizing your desire in any way, I'm just suggesting maybe that's why it's not available with this phone. Not much demand for reasons I stated.
Click to expand...
Click to collapse
I'm actually with you as far as temporarily installing it to test the ROM, however I have a rather annoying reason to still want it. The only ways to cash checks with my bank is to either physically mail the checks or deposit them by photo. As I'd rather have an automatic solution, I'm left with the latter. However, this leaves me with the problem that the camera doesn't work in their app on custom nougat ROMS (which I run). I tried talking their dev team into fixing it, but they reasonably don't want anything to do with supporting custom ROMS. As I'd rather not go through the whole backup/wipe/restore/repeat routine every time I want to cash a check, I am unfortunately left with dual booting a ROM that their app does support (most ROMS marshmallow or older).

I found another one that works (and finally works with my bank as well ). Here is the forum post for the Bliss ROM.

Stuckurface said:
Edit: I've found two that work with crdroid v3.3
Bliss xda post Specific tested ROM download
AOKP version list (there is no marshmallow xda post) Specific tested ROM download
Click to expand...
Click to collapse
Both of those ROMs are by @NepoRood. He posted them over here in the Droid Turbo forum instead of the other Quark forum as he owned a Droid Turbo. But so does @calsurferpunk, and he still posts his CM14/LOS ROM over in the other Quark forum. We used to be one big forum, but after the split most Quark development got posted over there as the Droid Turbo bootloader had not yet been unlocked by Sunshine. After the Sunshine team unlock, devs just continued posting over there for the most part...
@NepoRood shattered his Droid Turbo, and now has a different phone -- but you could ask him what he did differently to allow multi-ROM for those two Marshmallow ROMs that changed with his Nougat ROM. He said he was still going to post AOKP ROM updates with the help of testers in this forum.
Also, for his Nougat AOKP, make sure you are using his PERSONALIZED builds, not any of the "nightlies". To gain official status, he had to agree not to change anything in the AOKP ROM, but he was allowed to make and post personalized builds which have tweaks.
Last, you've tried all these? Current list of Nougat and Marshmallow. I didn't bother keeping track of Lollipop.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=71821604&postcount=73
___________
Stuckurface said:
I'm actually with you as far as temporarily installing it to test the ROM, however I have a rather annoying reason to still want it. The only ways to cash checks with my bank is to either physically mail the checks or deposit them by photo. As I'd rather have an automatic solution, I'm left with the latter. However, this leaves me with the problem that the camera doesn't work in their app on custom nougat ROMS (which I run).
Click to expand...
Click to collapse
OK, that's a practical reason I can understand.
So, it's nothing about "Safety Net" issues, it's basically newer custom ROMs (Nougat) don't work?
The app of the bank I use (a nationwide mega bank) works fine with RR 6.X (Marshmallow) and before that with CM12.1 (Lollipop) in depositing checks via photo. I've not tried Nougat ROMs yet. So, I may run into the same problem...
I've stayed with RR 6.x as it's rock solid and allows me to use a few xposed modules like Google Assistant Enabler (to turn on and unlock display), YouTube Adaway (to block YouTube ads, which regular Adaway does not) and MinMin Guard (which blocks 99.9% of all in app ads). I wish @bhb27 would release one more "rollup" update before development completely ends.
Of course I will switch to Nougat one day, but I didn't switch to Marshmallow until October of 2016, about the time Nougat was being released.

ChazzMatt said:
We used to be one big forum, but after the split most development got posted over there as the Droid Turbo bootloader had not yet been unlocked by Sunshine....
....Last, you've tried all these? Current list of Nougat and Marshmallow. I didn't bother keeping track of Lollipop.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=71821604&postcount=73
Click to expand...
Click to collapse
I knew that Moto Maxx and Droid Turbo were basically the same phone, but I always stuck to the Turbo forum for fear of bricking my phone/messing up my cell connectivity. I didn't realize that most of the ROMS are cross compatible :/
I tested a few of them but I never saw your list. Thanks for maintaining that, I just wish I had seen it sooner!
ChazzMatt said:
So, it's nothing about "Safety Net" issues, it's basically newer custom ROMs (Nougat) don't work?
Click to expand...
Click to collapse
Yep, I've got the photo check deposit to work on ROMS that don't pass safety net multiple times. The problem appears stem from the way custom nougat ROMS (and more specifically the way my bank app) interacts with the camera, though I haven't tried logging the app's behavior so your guess is as good as mine.

I miss Bliss, on my Turbo (heck, I miss my Turbo, lol)
Nougat ROMs have more security than Marshmallow, it's most likely Your bank app that is causing the problems though. I'm running Screw'D Nougat on my Nexus 6P and have no problems with using my banks mobile app (but, we're Rednecks, )
As far as MultiROM goes, I didn't do anything special to my builds, I don't know why Nougat doesn't work...

Stuckurface said:
I didn't realize that most of the ROMS are cross compatible :/
I tested a few of them but I never saw your list. Thanks for maintaining that, I just wish I had seen it sooner!
Click to expand...
Click to collapse
All the ROMs (especially Marshmallow and Nougat) are cross compatible for all Quarks -- except for CF's Verizon stock-based ROM. This is thanks to the CM dev @Skrilax_CZ who adapted the Motorola kernel so all CM (now LOS) based ROMs would work for all Quarks, after Sunshine team unlocked the Droid Turbo bootloader. @bhb27 has continued that work. Even ROMS like "AOSP" still all use that "universal" kernel coding for all Quark ROMs. Again, the exception is CF's ROM, which are purely Verizon stock firmware, just debloated and tweaked.
There was one older Lollipop ROM that never got updated with the "universal" kernel (after the November 2015 Droid Turbo bootloader unlock), but even CM12.1 (Lollipop), RR Lollipop, and @calsurferpunk's "unofficial" CM12.1 was also cross-compatible with all Quarks.

Multi-ROM has now been released by @bhb27, plus we now have SEVEN Nougat ROMs.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=73459132&postcount=80