Related
I want to triple boot my Galaxy S3 with the following:
A modded stock ROM
MIUI
AOKP or CM (Which is more customizable? I'll choose that.)
How on earth do I do it?
BTW calling not working well in MIUI
I don't think you can do that at least not on i9300
At most dual boot
Press thanx if i helped you in anyway...
yoyololo said:
I want to triple boot my Galaxy S3 with the following:
A modded stock ROM
MIUI
AOKP or CM (Which is more customizable? I'll choose that.)
How on earth do I do it?
BTW calling not working well in MIUI
Click to expand...
Click to collapse
in the past there was announced triple boot for devil kernel, but it has been quite a long time since then, and there hasn't been an update for some time now as well. but it was also announced that development continues again in nfuture so maybe your wish come true
(but i am not sure if miui is even supported there)
IMO it will be quite annoying to always switch between 3 roms. atm it is even annoying for me to switch between 2 roms.
@yoyololo
I wouldn't recommend dual-booting for most people, and triple-booting will just be a nightmare. There is a risk of permanently damaging your phone if done incorrectly.
RazorMC said:
@yoyololo
I wouldn't recommend dual-booting for most people, and triple-booting will just be a nightmare. There is a risk of permanently damaging your phone if done incorrectly.
Click to expand...
Click to collapse
So My final decision is Stock + AOKP
Possible?
So I saw this kernal called "SiyahKernel" that lets you dual-boot... How do I use it?
yoyololo said:
So I saw this kernal called "SiyahKernel" that lets you dual-boot... How do I use it?
Click to expand...
Click to collapse
Not siyah.Googy max would be necessary if you want to use the latest roms.
Try following instructions on the thread or better watch some videos for that on youtube
Press thanx if i helped you in anyway...
kunal1540 said:
Not siyah.Googy max would be necessary if you want to use the latest roms.
Try following instructions on the thread or better watch some videos for that on youtube
Press thanx if i helped you in anyway...
Click to expand...
Click to collapse
I've used this "Googy2-max"/"Googy-max2" (I forgot the name). I want to use SiyahMod for quadboot (Stock, AOKP, CM, PA, I know I can just use PAC, but it WON'T WORK) but it's not compatible. I tried...
yoyololo said:
So My final decision is Stock + AOKP
Possible?
Click to expand...
Click to collapse
Like @kunal1540 said, use GoogyMax kernel.
This will work for stock and aokp, but check which versions are supported. It is not possible to just use any version of the ROM directly. You need to check which ones will work from kernel's instructions.
RazorMC said:
Like @kunal1540 said, use GoogyMax kernel.
This will work for stock and aokp, but check which versions are supported. It is not possible to just use any version of the ROM directly. You need to check which ones will work from kernel's instructions.
Click to expand...
Click to collapse
Done it
Nice
.
This is the place for Q&A, general discussions, and post-installation chat about JasmineROM. Please keep your personal issues that are not related to the development, such as themes and other stuff, here.
.
Looks great. Will drive it for a few days and report back if there's any issues.
Thanks for all of your hard work & our 1st ROM.
Will be a version for the D855 ?
drmspidi said:
Will be a version for the D855 ?
Click to expand...
Click to collapse
I don't have this device, but you may test it yourself. Make nandroid backup, clean flash & report me back! It doesn't flash any firmware images (kernel, modem, ... etc); so, it's safe to test on other devices. If you've any issues, you can restore your backup.
DPI Affect
Heard mention that the DPI change affects the quick circle case display......is this true, or would it affect this? If it does change, what can be done post flashing to regain quick circle proper display?
Thanks for the work, btw!!!
hsbadr said:
I don't have this device, but you may test it yourself. Make nandroid backup, clean flash & report me back! It doesn't flash any firmware images (kernel, modem, ... etc); so, it's safe to test on other devices. If you've any issues, you can restore your backup.
Click to expand...
Click to collapse
But isn' t only for Verizon ?
What kind of problem I may have ?
JasmineRom
drmspidi said:
But isn' t only for Verizon ?
What kind of problem I may have ?
Click to expand...
Click to collapse
Yes this Rom is for the Verizon VS985 variant but he just stated that it does not flash a kernel, modem, or recovery of any sort. So the worst thing that may happen is your device bootloops or you just may not have data, working WiFi or Bluetooth, or some other minor issue. It is relatively safe to flash on other devices to try so long as you have a Nandroid backup of a working or stock ROM.
willyjay said:
Heard mention that the DPI change affects the quick circle case display......is this true, or would it affect this? If it does change, what can be done post flashing to regain quick circle proper display?
Thanks for the work, btw!!!
Click to expand...
Click to collapse
It works fine for me, but I can create a flashable zip to revert to stock DPI, if needed.
drmspidi said:
But isn' t only for Verizon ?
Click to expand...
Click to collapse
Yes, some Verizon devices may work on other carriers.
drmspidi said:
What kind of problem I may have ?
Click to expand...
Click to collapse
Unpredictable, it may work perfect or with issues related to hardware drivers: mainly Mobile Data, WiFi, bluetooth, ... etc. It could be fixed though with a converter replacements (port).
acparker18 said:
Yes this Rom is for the Verizon VS985 variant but he just stated that it does not flash a kernel, modem, or recovery of any sort. So the worst thing that may happen is your device bootloops or you just may not have data, working WiFi or Bluetooth, or some other minor issue. It is relatively safe to flash on other devices to try so long as you have a Nandroid backup of a working or stock ROM.
Click to expand...
Click to collapse
Exactly.
add ons
Do you think you will be adding volume enhancements soon?
Loving the Rom. Just needs themes and home back up and restore enabled
Saw that you would be pushing 1.0.1 update for tether. Will this just be an update zip or will it require a full rom flash?
USB Debugging Doesn't Stick After Reboot
I attempted to get USB Debugging to stick after rebooting by adding this line to build.prop:
persist.service.adb.enable=1
I reset the permissions to rw-r-r after editing build.prop before I rebooted. No luck, still not remaining enabled after a reboot.
lawtalking said:
Saw that you would be pushing 1.0.1 update for tether. Will this just be an update zip or will it require a full rom flash?
Click to expand...
Click to collapse
1.01 or 1.1 will be an update zip to dirty flash...
The Great Dahli llama said:
I attempted to get USB Debugging to stick after rebooting by adding this line to build.prop:
persist.service.adb.enable=1
I reset the permissions to rw-r-r after editing build.prop before I rebooted. No luck, still not remaining enabled after a reboot.
Click to expand...
Click to collapse
I'm aware of this issues...
I hope you can get Aroma working later on. The only downside is the size of the rom for download. The only bloat I find useful on this phone is multi window, knock on, and the clipboard. I hope to see some kind of volume enhancement as well.
wes53177 said:
Do you think you will be adding volume enhancements soon?
Click to expand...
Click to collapse
jerbear2011 said:
Loving the Rom. Just needs themes and home back up and restore enabled
Click to expand...
Click to collapse
eraursls1984 said:
I hope you can get Aroma working later on. The only downside is the size of the rom for download. The only bloat I find useful on this phone is multi window, knock on, and the clipboard. I hope to see some kind of volume enhancement as well.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Sure, at some point a new release of JasmineROM will include all requested features
Oh also the Verizon variants messaging app doesn't allow you to choose vibe pattern if there's a way you could enable that it would be awesome.
Sent from my Bump'd VS985 4G
I've got the itch to do a bit of themeing. Do you guys use the G3 TweaksBox themes? Im considering building for that since it is cross ROM compatible.
It will be a black/grey/orange theme using the Numix Cinnamon theme as inspiration.
Would there be an issue if I change the DPI to the original value.
I don't like the one with the ROM, and I can't get used to it.
What would be the best way to go about it?
jerbear2011 said:
Oh also the Verizon variants messaging app doesn't allow you to choose vibe pattern if there's a way you could enable that it would be awesome.
Click to expand...
Click to collapse
will look into it...
PiousInquisitor said:
I've got the itch to do a bit of themeing. Do you guys use the G3 TweaksBox themes? Im considering building for that since it is cross ROM compatible.
It will be a black/grey/orange theme using the Numix Cinnamon theme as inspiration.
Click to expand...
Click to collapse
Most apps/themes should work with this ROM since it's deodexed, except carrier-related apps: messaging, *telephony*, ... etc. I'll make my own themes & a list of compatible themes later.
Umbrella Corp said:
Would there be an issue if I change the DPI to the original value.
I don't like the one with the ROM, and I can't get used to it.
What would be the best way to go about it?
Click to expand...
Click to collapse
1.0.1 includes what you want; http://forum.xda-developers.com/showpost.php?p=56028380&postcount=129
This ROM ROCKS!!!! Thx!!!!
having the same problem with all pie roms. messenger and whatsapp keeps getting closed in the background, also doesn't give me notifications. I made them "not optimized" in battery optimization but it didn't help.
Same problem here. Running AEX 6.1. with DA kernel.
DragonTerror said:
Same problem here. Running AEX 6.1. with DA kernel.
Click to expand...
Click to collapse
yeah I am on AEX too, but its a common problem through out all roms for me.
@DragonTerror do you use Titanium Backup?
q.sadid said:
@DragonTerror do you use Titanium Backup?
Click to expand...
Click to collapse
No. Never used it...
q.sadid said:
yeah I am on AEX too, but its a common problem through out all roms for me.
Click to expand...
Click to collapse
Try dark ages kernal
Fixed same problem for me on oreo roms
bot88 said:
Try dark ages kernal
Fixed same problem for me on oreo roms
Click to expand...
Click to collapse
DA gives me screen ghost/burn in problems. okay I will try DA again and see if it works. thanks for the reply.
q.sadid said:
DA gives me screen ghost/burn in problems. okay I will try DA again and see if it works. thanks for the reply.
Click to expand...
Click to collapse
As far as i know ghosting problem is related to older firmware, try to update that as well
Cheers
bot88 said:
As far as i know ghosting problem is related to older firmware, try to update that as well
Cheers
Click to expand...
Click to collapse
Tried DA kernel, still the same problem ?
qazi_sadid said:
Tried DA kernel, still the same problem
Click to expand...
Click to collapse
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
3. Maybe a hardware related problem
4. Restoration of apps using titanium backup
5. Wrong Wake lock blocker settings which prevent phone form waking up on critical wakelock such as gmscore wake locks, which will definitely results in delayed notifications (tested by myself)
Maybe gms dose for magisk can also be responsible.
bot88 said:
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
3. Maybe a hardware related problem
4. Restoration of apps using titanium backup
5. Wrong Wake lock blocker settings which prevent phone form waking up on critical wakelock such as gmscore wake locks, which will definitely results in delayed notifications (tested by myself)
Maybe gms dose for magisk can also be responsible.
Click to expand...
Click to collapse
Here's my situation:
1. I placed latest global firmware I could get my hands on. I'm not sure was it beta or stable.
2. This is a GApps issue?
3. I'm pretty sure it's not since I came from Havoc 2.0 just 2 weeks ago. Before AEX 6.1 it worked normally.
4. I used Migrate to restore apps.
5. I don't use any wake lock blocker whatsoever
DragonTerror said:
Here's my situation:
1. I placed latest global firmware I could get my hands on. I'm not sure was it beta or stable.
2. This is a GApps issue?
3. I'm pretty sure it's not since I came from Havoc 2.0 just 2 weeks ago. Before AEX 6.1 it worked normally.
4. I used Migrate to restore apps.
5. I don't use any wake lock blocker whatsoever
Click to expand...
Click to collapse
Try latest gapps, or different packages, (mini or micro)
Maybe that can help
:fingers-crossed:
bot88 said:
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
.............................
Maybe gms dose for magisk can also be responsible.
Click to expand...
Click to collapse
tried everything. tried your solution. tried this Post too : https://forum.xda-developers.com/redmi-note-5/development/rom-havocos-t3807696/post78675837
BUT nothing is working. either its the dosing system they are using in the rom is responsible for this, or the hardware of my phone. I am currrently one AEX 6.2 with DA kernel
q.sadid said:
tried everything. tried your solution. tried this Post too : https://forum.xda-developers.com/redmi-note-5/development/rom-havocos-t3807696/post78675837
BUT nothing is working. either its the dosing system they are using in the rom is responsible for this, or the hardware of my phone. I am currrently one AEX 6.2 with DA kernel
Click to expand...
Click to collapse
I'm pretty sure it's a ROM problem. Tried running without DA kernel and literally nothing changed, except my battery life which worsened a bit. Hoping for a solution or I'm going back to Havoc OS
DragonTerror said:
I'm pretty sure it's a ROM problem. Tried running without DA kernel and literally nothing changed, except my battery life which worsened a bit. Hoping for a solution or I'm going back to Havoc OS
Click to expand...
Click to collapse
I will go back to MIUI 10 tomorrow and see if the problem remains, it will make sure its a pie rom problem.
q.sadid said:
I will go back to MIUI 10 tomorrow and see if the problem remains, it will make sure its a pie rom problem.
Click to expand...
Click to collapse
try havoc os 2.1
latest change log suggest addition of "xiaomi doze" maybe that will help.
bot88 said:
try havoc os 2.1
latest change log suggest addition of "xiaomi doze" maybe that will help.
Click to expand...
Click to collapse
Will do tommorow if I find time for it
I will post my results.
I tried every rom pie rom but couldn't get any of them to work
Below are Stock kernels with DT2W added. The kernels have been extracted from 47.2.A.11.228 firmware.
The kernels are SElinux enforcing (same as stock). They are in no way custom, all i have done is add the dtb from Iovf's .107 kernel to allow double tap 2 wake.
Some people have reported the DT2W feature requires a solid tap, and sometimes may not wake the screen instantly.
This is out of my hands, and capabilities, to do anything about.
Installation:
On stock .228 firmware:
Flash the kernel for your device in TWRP
Flash whatever Magisk.zip you prefer, and reboot. Once rebooted, install the magisk module below (DT2W_Magisk Module) and reboot.
(If you want permissive selinux, also install the Permissive module in Magisk at the same time).
eXistenZ users:
The kernels are also compatible. Same install steps apply (flash kernel, flash magisk, reboot)
If.you want to keep SElinux set to enforcing, use the DT2W_Magisk Module.
If you are using something to set SElinux to permissive for fonts (or whatever reason), you dont need the DT2W Magisk Module, only the Permissive module.
Also attached are the TWRP flashable stock .228 kernels.
Thanks to @iovf for the original kernels I pinched parts from.
Thanks to @shoey63 for the DT2W Magisk Module.
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Did you flash magisk after kernel?
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Which kernel? Single or dual?
kojak1989 said:
Did you flash magisk after kernel?
Click to expand...
Click to collapse
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Beetle84 said:
Which kernel? Single or dual?
Click to expand...
Click to collapse
Single
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
Did tou do it with clean install ? If yes then you must do it with 18.1 and let eXistenZ boot once and for me iovf kernel make freezes.
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
I use v20 on the XZP with no drama, can you try the dual sim kernel and let me know? There is no harm in using a dual kernel on a single sim phone. Thanks.
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
Myself5 said:
I roughly remember looking into this decades ago and the conclusion was that either the XZP/XZ1 kernel is super ****ed (beyond repair) or they have some sort of hardware issue causing the situations. When you used DT2W and combined it with using the power button in a specific order the touchscreen wouldn't work anymore until you turn the screen off/on again using the power button.
Click to expand...
Click to collapse
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Generic123. said:
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Click to expand...
Click to collapse
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Generic123. said:
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Click to expand...
Click to collapse
Will do
Beetle84 said:
Will do
Click to expand...
Click to collapse
Many thanks my dude.
I'm bit courious, as there has been only one person has mentioned what rom and firmware they are using, but for those that are using the the existenz rom have you tried going into the rom display settings and flipping on the dt2w switch to see if it helps..
see pic..
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
theflanker said:
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
Click to expand...
Click to collapse
No idea mate, single and dual are confirmed working. Try flashing the stock kernel, magisk and reboot
Then try the dt2w kernel, magisk and reboot.
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
See above.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Myself5 said:
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
See above.
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Click to expand...
Click to collapse
Thanks for the clarification. Would it be possible for us to determine what our touchscreen manufacturers are? In your case, tap to wake is pretty glitchy. But, in @Beetle84's case, he appears to have little/no issues. It would be nice to see if different touchscreen manufacturers are at play here.
Can I change it? Most of the times it doesnt work like it's supposed to. Is there any other alternative besides buttons on the screen? I'm on stock miui 11.08.
Thanks.
Are you on stock kernel? Afaik there are custom kernels who are in conflict with miui gestures
BatZzn said:
Are you on stock kernel? Afaik there are custom kernels who are in conflict with miui gestures
Click to expand...
Click to collapse
Yes, stock, locked bootloader, no root.
Ok that's strange. You can enable quick ball feature in miui and customize the desired buttons:
https://c.mi.com/thread-1426458-1-0.html
BatZzn said:
Ok that's strange. You can enable quick ball feature in miui and customize the desired buttons:
https://c.mi.com/thread-1426458-1-0.html
Click to expand...
Click to collapse
This is nice. I'll try to get used to it. Thank you!