I know the VR isn't guaranteed to work with rooted phones, but I'm on a stock deodexed lollipop rom with xposed enabled and the gear VR does not split into side by side mode when plugged into the gear VR.
Any idea what the issue could be? Again, stock rom, just deodexed, with xposed.
Try flashing a kernel that's what I had to do.
Pretty sure I'm using the stock kernel. Can you link to the one you flashed? Much appreciated.
holycow1 said:
Pretty sure I'm using the stock kernel. Can you link to the one you flashed? Much appreciated.
Click to expand...
Click to collapse
Google emotion kernel, has been working well for me
I have been using ael kernel working great
Is the issue rooted phones, or custom roms? Seems just rooting should not impact anything. Rooted with stock rom should be no problem.
rushless said:
Is the issue rooted phones, or custom roms? Seems just rooting should not impact anything. Rooted with stock rom should be no problem.
Click to expand...
Click to collapse
It's not the root that does it, as explained earlier something happens within the kernel that impacts VR mode. I'm on a stock deodexed and I thought I had a faulty unit before I flashed the emotion kernel
Good to know
Related
Alright, so I've enjoyed modding my Android devices since I got my first Android running on 2.2, especially because of the options to tweak CPU usage, and just (from what I have noticed) better general usage with all of my devices. I purchased this phone because of it's similar power usage to the S4 and it being water & dust resistant. However, most of the development that I have seen for this forum has been for the i9525, which is the international version. I have the i537, and have been going crazy with battery drainage issues, and I think only a custom kernel/new ROM can fix this. Could somebody point me in the right direction of where to go? I've heard talk that after MF2, installing Safestrap right now is essentially not possible, due to bootloader issues.
I'm running the Stock ROM v 4.2.2
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
QuentinX5 said:
Alright, so I've enjoyed modding my Android devices since I got my first Android running on 2.2, especially because of the options to tweak CPU usage, and just (from what I have noticed) better general usage with all of my devices. I purchased this phone because of it's similar power usage to the S4 and it being water & dust resistant. However, most of the development that I have seen for this forum has been for the i9525, which is the international version. I have the i537, and have been going crazy with battery drainage issues, and I think only a custom kernel/new ROM can fix this. Could somebody point me in the right direction of where to go? I've heard talk that after MF2, installing Safestrap right now is essentially not possible, due to bootloader issues.
I'm running the Stock ROM v 4.2.2
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
SafeStrap works for every version of firmware for the i537, you just need to use the proper version. If you're on ML2 I think you need 3.71, but please check to make sure because I could be wrong. As for a custom kernel or tweaking the CPU, it's not going to be possible on the i537 because the bootloader is locked and you are forced to use the stock kernel. You can try a custom ROM through SafeStrap, but I don't think it's going to help much. You might be better off upgrading the NE3 or NH3 and trying a custom ROM through SafeStrap there.
Devo7v said:
SafeStrap works for every version of firmware for the i537, you just need to use the proper version. If you're on ML2 I think you need 3.71, but please check to make sure because I could be wrong. As for a custom kernel or tweaking the CPU, it's not going to be possible on the i537 because the bootloader is locked and you are forced to use the stock kernel. You can try a custom ROM through SafeStrap, but I don't think it's going to help much. You might be better off upgrading the NE3 or NH3 and trying a custom ROM through SafeStrap there.
Click to expand...
Click to collapse
So essentially until we get the bootloader unlocked and can install a custom recovery (Like CWM or TWRP, instead of using SafeStrap), no "real" custom ROMs? More just ROMs based off of the stock kernel/modem/etc.?
QuentinX5 said:
So essentially until we get the bootloader unlocked and can install a custom recovery (Like CWM or TWRP, instead of using SafeStrap), no "real" custom ROMs? More just ROMs based off of the stock kernel/modem/etc.?
Click to expand...
Click to collapse
Correct, and most of the people who were leading the development and research of unlocking the bootloader have decided to move on to other things within the last week. At this point it looks like the bootloader will never be unlocked. There's always a slim chance but it's not looking good.
Hey fellows,
After having the Gear VR sitting at my desk for a couple of days I finally received my Note 4 (N910F). Updated it to Lollipop right away and afterwards tested the Gear VR, which was working just fine.
As the stock rom didn't gave me the freedom I needed / wanted I rooted it and installed a custom rom (EchoePop). After setting everything up I tried to fire up the VR. Installing the apps etc was no big deal. As soon as I plugged it into the VR I heard the sound and see the blue start screen. This only gives me the loading graphic and doesn't go any further.
Because I thought they might removed this service as part of their de-bloating I installed the Alexndr Lollipop because it's a stock rom that only removed apps that you can find in the Play Store. Same procedure here but also the same result.
The kernel shouldn't be a problem here, I guess. Besides from the fact that there is no lollipop custom kernel available yet?!
Did someone have a similar experience and knows the solution for it? I hope it's not an overall issue with custom rom.
Thanks,
FutureBSD
Doesn't work with stock lollipop either. Tried stock then custom odexed and deodexed. From what I read it is kernel related, sammy sent the kernel to oculus to mod it for gear vr which was the reason for the lolipop delay. Hopefully it will be fixed in the next round of lolipop releases, pretty sure that's why the USA variants don't have lolipop yet.
Ah alright. I heard the rumors that they delayed the Lollipop release because of this. As they released Lollipop I was just assuming that it had been fixed. And I thought I tested it after updating to Lollipop. Well, maybe I mixed that up.
I was the same but all i can think of is maybe the vr isn't released in Germany so they released it there first and are waiting for oculus to fix the kernel before the next round of releases. Really hope so as I've had to go back to kk
The VR has been released in Germany. I ordered it there as I live in Germany. Also I just read on Reddit that people have it working on Lollipop but it doesn't seem to be the best experience.
Wow can you link me please as I don't know anyone who has it working on lollipop. Would like to know how they did it
Sure thing. I post the link to the discussion on Reddit and the Oculus forum. It's the same topic but the official Oculus forum might be the better source for quicker official updates.
Topic on the Oculus forum
Topic on Reddit
Now I'm back to zero and have to figure out what the problem is.
FutureBSD said:
Sure thing. I post the link to the discussion on Reddit and the Oculus forum. It's the same topic but the official Oculus forum might be the better source for quicker official updates.
Topic on the Oculus forum
Topic on Reddit
Now I'm back to zero and have to figure out what the problem is.
Click to expand...
Click to collapse
Wonder if it's exynos and snapdragon? Maybe works ok on exynos. I've tried everything and it just won't launch for me
This is something specific to an item that's removed in the custom rom. I had this exact issue on Exynos as well, custom rom was blue screen, then shaded black/blue screen, both static.
Flashing a rooted stock made it magically work.
Domen Lo said:
This is something specific to an item that's removed in the custom rom. I had this exact issue on Exynos as well, custom rom was blue screen, then shaded black/blue screen, both static.
Flashing a rooted stock made it magically work.
Click to expand...
Click to collapse
That's what I was thinking. That's why I went for the Alexndr Rom. He didn't debloat so much. It's almost like the stock. But maybe I will try the stock rom again.
Maybe a Csc issue?
FutureBSD said:
That's what I was thinking. That's why I went for the Alexndr Rom. He didn't debloat so much. It's almost like the stock. But maybe I will try the stock rom again.
Click to expand...
Click to collapse
Looks like it's root that breaks it
Domen Lo said:
This is something specific to an item that's removed in the custom rom. I had this exact issue on Exynos as well, custom rom was blue screen, then shaded black/blue screen, both static.
Flashing a rooted stock made it magically work.
Click to expand...
Click to collapse
Why fight it guys, just go stock rooted. You can add many of the best goodies yourself anyway using xPosed Modules. Lollipop is so damn fast and pretty on it's own the benefits of debloat and all that aren't as significant anyway. I'm sure they'll sort it eventually. Good luck.
sawdoctor said:
Looks like it's root that breaks it
Click to expand...
Click to collapse
This is incorrect, I am currently rooted and everything works fine. Well, better than fine, since I am able to do rooty things.
Domen Lo said:
This is incorrect, I am currently rooted and everything works fine. Well, better than fine, since I am able to do rooty things.
Click to expand...
Click to collapse
Wierd it never worked for me at all on lollipop and all I did was root stock
I'm currently checking with _Alexndr what has been touched by him during creation. But maybe it's just something simple like the Device status that's changing from Original to Custom. Wouldn't be surprised after all the Knox warranty crap
sawdoctor said:
Wierd it never worked for me at all on lollipop and all I did was root stock
Click to expand...
Click to collapse
Did you full wipe prior to flashing the rom? When restoring your apps, did you uncheck data and make sure you didn't restore any system apps? Any conflict could be breaking things. Have you tried flashing the rom clean and running GVR prior to restoring anything? Are you running Xposed or does it come with the rom? That has a history of causing problems on occasion. Try deleting it and see what happens.
** I know you're an experienced user and this stuff is probably obvious to you. Just throwing out ideas. Almost 4,000 thanks and you're not a developer? I'm impressed.
mitchellvii said:
Did you full wipe prior to flashing the rom? When restoring your apps, did you uncheck data and make sure you didn't restore any system apps? Any conflict could be breaking things. Have you tried flashing the rom clean and running GVR prior to restoring anything? Are you running Xposed or does it come with the rom? That has a history of causing problems on occasion. Try deleting it and see what happens.
** I know you're an experienced user and this stuff is probably obvious to you. Just throwing out ideas. Almost 4,000 thanks and you're not a developer? I'm impressed.
Click to expand...
Click to collapse
I didn't wipe when i used odin and obviously never restored anything. I did full wipe on every twrp flashable zip I've flashed though. I've flashed deodexed and odexed roms both made with archi that were just plain rooted stock with only busybox and init.d support added.
sawdoctor said:
I didn't wipe when i used odin and obviously never restored anything. I did full wipe on every twrp flashable zip I've flashed though. I've flashed deodexed and odexed roms both made with archi that were just plain rooted stock with only busybox and init.d support added.
Click to expand...
Click to collapse
When you Odin Stock it leaves your setup intact, doesn't it? Maybe if you full wipe then Odin stock it will work for you?
mitchellvii said:
When you Odin Stock it leaves your setup intact, doesn't it? Maybe if you full wipe then Odin stock it will work for you?
Click to expand...
Click to collapse
I know that's what I was thinking. Tbh I'm staying on kk till sammy release the kernel source anyway, can't user viper sound without permissive kernel and still no xposed for sammy kk yet
I just bought the gear vr for my note 4 and i was wondering if i could have comoatibilty problems with the X note custom rom I am currently using.
Thanks in advance
Not all custom roms work with the Gear VR. First of all such rom MUST be based on Touchwiz and have a specific kind of kernel. In my case I'm using FireKat v13 along with AEL Kernel. Working great with the VR.
Sent from my SM-N910T using Tapatalk
I'm using PopRocks rom on my Note4 and the gear didn't work with the stock kernel in PopRocks rom (stuck at the Health and warning screen in GVR). But it works perfectly with the Emotion kernel (v1.18).
gnash.s said:
I'm using PopRocks rom on my Note4 and the gear didn't work with the stock kernel in PopRocks rom (stuck at the Health and warning screen in GVR). But it works perfectly with the Emotion kernel (v1.18).
Click to expand...
Click to collapse
I have a SM-N910T and right now I'm using FireKat and AEL kernel, but it looks like, with Netflix requiring Lollipop, I'll need to upgrade soon. PopRocks seems like what I want, I'm just worried that I'll be missing the Adreno GPU driver fix that they pushed in 5.1.1 (which T-Mobile doesn't have yet...) This is what pushed me to use FireKat in the first place, since I was having lots of performance and compatibility issues with Gear VR after upgrading to stock Lollipop.
Does performance seem okay on your setup?
vermadas said:
I have a SM-N910T and right now I'm using FireKat and AEL kernel, but it looks like, with Netflix requiring Lollipop, I'll need to upgrade soon. PopRocks seems like what I want, I'm just worried that I'll be missing the Adreno GPU driver fix that they pushed in 5.1.1 (which T-Mobile doesn't have yet...) This is what pushed me to use FireKat in the first place, since I was having lots of performance and compatibility issues with Gear VR after upgrading to stock Lollipop.
Does performance seem okay on your setup?
Click to expand...
Click to collapse
Yeah, I was also on FireKAT since the v1 and jumped on to PopRocks from v1. PR has been pretty stable and smooth. With the emotion kernel, I'm using the Thermal controls and the under-voltage setting as well to keep the Note cooler while using it in GearVR. I usually dirty flash from different versions and if I see any issues, then I clean flash again. Even with the xposed (I need it for exchange bypass) I would say it is pretty stable.
gnash.s said:
Yeah, I was also on FireKAT since the v1 and jumped on to PopRocks from v1. PR has been pretty stable and smooth. With the emotion kernel, I'm using the Thermal controls and the under-voltage setting as well to keep the Note cooler while using it in GearVR. I usually dirty flash from different versions and if I see any issues, then I clean flash again. Even with the xposed (I need it for exchange bypass) I would say it is pretty stable.
Click to expand...
Click to collapse
Can you share your Emotion kernel? I'm on poprocks v9 right now and just want to get GearVR running again. Used AEL on FK which worked fine.
If I do a Nandroid back-up of just the kernel before install of Emotion, I should be able to restore and get back to stock right?
Looking into cooling mods using a fan so I can play longer. Thinking of buying a backcover and doing a fan mod, so I don't need to cut the cover. Reading up where it gets hot the most for fan positioning.
sfsilicon said:
Can you share your Emotion kernel? I'm on poprocks v9 right now and just want to get GearVR running again. Used AEL on FK which worked fine.
If I do a Nandroid back-up of just the kernel before install of Emotion, I should be able to restore and get back to stock right?
Looking into cooling mods using a fan so I can play longer. Thinking of buying a backcover and doing a fan mod, so I don't need to cut the cover. Reading up where it gets hot the most for fan positioning.
Click to expand...
Click to collapse
Yeah, but I would probably make a full nandroid backup just in case if something goes wrong.
Sure, I just downloaded directly from the link in the emotion kernel thread, using the v19 rc1.
Note 4, 5.0.1
https://www.mediafire.com/folder/rvxdm018fdm1o/EMOTION_KERNELS_NOTE4#17x02pnhs2ype
Thread
http://forum.xda-developers.com/note-4/orig-development/tw-kernel-emotroid-team-t2990557
Cheers
Sent from my SM-N910T using Tapatalk
My note 4 is now android 5.1.1 , and I heard that you must flash custom Kernel to avoid boot loop when rooting android 5.1.
I don't know where to start, can anyone please tell me what the current most stable, fast and battery friendly solution for Note 4?
What I can think of so far are:
1. root + custom kernel+some way to debloat
2. Stock debloated TW rom like: http://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538
3. Modified stock debloated TW rom like: http://forum.xda-developers.com/note-4-tmobile/development/moving-please-dont-post-t2943845
4. Custom rom like cm: https://download.cyanogenmod.org/?device=trltetmo
ps: Apart from custom kernel, can we also root 5.1.1 note 4 by Install 5.0.1 Bootloader ? http://forum.xda-developers.com/note-4/development/root-5-1-1-n910c-t3190520 Is there some other ways that I'm not being aware of?
inonosa said:
My note 4 is now android 5.1.1 , and I heard that you must flash custom Kernel to avoid boot loop when rooting android 5.1.
I don't know where to start, can anyone please tell me what the current most stable, fast and battery friendly solution for Note 4?
What I can think of so far are:
1. root + custom kernel+some way to debloat
2. Stock debloated TW rom like: http://forum.xda-developers.com/note...ooted-t3025538
3. Modified stock debloated TW rom like: http://forum.xda-developers.com/note...-post-t2943845
4. Custom rom like cm: https://download.cyanogenmod.org/?ty...evice=trltetmo
ps: Apart from custom kernel, can we also root 5.1.1 note 4 by Install 5.0.1 Bootloader ? http://forum.xda-developers.com/note...n910c-t3190520 Is there some other ways that I'm not being aware of?
Click to expand...
Click to collapse
If it helps, I rooted and installed a modified international TW ROM. I lose wifi calling. (Never used it) Lose Tmobile hotspot (FoxFi replaces this just fine) Other then adding the APN manually and changing the region in my build.prop to US, it was pretty straight forward. If you want debloat, just root, add TWRP, wipe the stock rom and add a custom one. I prefer modified TW because of stability. I flashed the international because its 5.1.1. So far it runs very well. The ROM I flashed required no additional flashing of a kernel . Look at my sig for the ROM im currently on
LoopDoGG79 said:
If it helps, I rooted and installed a modified international TW ROM. I lose wifi calling. (Never used it) Lose Tmobile hotspot (FoxFi replaces this just fine) Other then adding the APN manually and changing the region in my build.prop to US, it was pretty straight forward. If you want debloat, just root, add TWRP, wipe the stock rom and add a custom one. I prefer modified TW because of stability. I flashed the international because its 5.1.1. So far it runs very well. The ROM I flashed required no additional flashing of a ROM. Look at my sig for the ROM im currently on
Click to expand...
Click to collapse
That is what I thought, and i'm getting Modified stock debloated TW rom, RAPTURE
inonosa said:
That is what I thought, and i'm getting Modified stock debloated TW rom, RAPTURE
Click to expand...
Click to collapse
I was running Darthstalker for months. It ran well for the most part. I heard there was several android bug fixes from 5.0.1 to 5.1.1 that make running a ROM more user friendly.
Sent from my SM-N910F using Tapatalk
inonosa said:
My note 4 is now android 5.1.1 , and I heard that you must flash custom Kernel to avoid boot loop when rooting android 5.1.
I don't know where to start, can anyone please tell me what the current most stable, fast and battery friendly solution for Note 4?
What I can think of so far are:
1. root + custom kernel+some way to debloat
2. Stock debloated TW rom like: http://forum.xda-developers.com/note...ooted-t3025538
3. Modified stock debloated TW rom like: http://forum.xda-developers.com/note...-post-t2943845
4. Custom rom like cm: https://download.cyanogenmod.org/?ty...evice=trltetmo
ps: Apart from custom kernel, can we also root 5.1.1 note 4 by Install 5.0.1 Bootloader ? http://forum.xda-developers.com/note...n910c-t3190520 Is there some other ways that I'm not being aware of?
Click to expand...
Click to collapse
I have a group on Google+ that is dedicated to debloating ROMs send me a PM if you are interested.
ShrekOpher said:
I have a group on Google+ that is dedicated to debloating ROMs send me a PM if you are interested.
Click to expand...
Click to collapse
thanks man, just the backing up/restoring the app+data had turned me off......
I think that I will stay with RAPTURE before something Major went wrong.
but what is your recommended rom?
inonosa said:
thanks man, just the backing up/restoring the app+data had turned me off......
I think that I will stay with RAPTURE before something Major went wrong.
but what is your recommended rom?
Click to expand...
Click to collapse
I'm using TEKHD right now. It's good 5.1.1 with good battery life, but really its just to hold me over till 6.0 drops either CM or TW.
Sent from my GT-N7105 using XDA Free mobile app
My Note 4 is the older 910T variant. It is still running 5.0.1. I have not taken the 5.1.1 update yet which I blocked using the Debloater. I have not rooted yet because I have a pending warranty issue (GPS) I need to take care of.
Here is my question. Is the root method for 5.0.1 inherently better than that of 5.1.1? If I understand correctly, the 5.1.1 method is systemless and does not use/require a custom kernel and some apps may not play well with this, such as Viper for Android.
I am concerned about this because I suspect Samsung may replace my 910T with a 910T3. This should solve my GPS problems but it seems that it may put me in a less advantageous rooting situation.
Am I correct on this? Can anyone shed light on this for me?
Thanks.
Rootabaga said:
My Note 4 is the older 910T variant. It is still running 5.0.1. I have not taken the 5.1.1 update yet which I blocked using the Debloater. I have not rooted yet because I have a pending warranty issue (GPS) I need to take care of.
Here is my question. Is the root method for 5.0.1 inherently better than that of 5.1.1? If I understand correctly, the 5.1.1 method is systemless and does not use/require a custom kernel and some apps may not play well with this, such as Viper for Android.
I am concerned about this because I suspect Samsung may replace my 910T with a 910T3. This should solve my GPS problems but it seems that it may put me in a less advantageous rooting situation.
Am I correct on this? Can anyone shed light on this for me?
Thanks.
Click to expand...
Click to collapse
You are correct in that 5.1.1 stock kernel requires systemless root. There is at least one kernel out there that is very close to stock that will accept system root, the name of which I can't remember.
I found systemless root to be almost completely functional, but did hit a roadblock or two (like V4a). Stock kernel is so much better than any other I've tried on touchwiz that its the only one I care to use, though I've given up on touchwiz completely as of late.
There are plenty of touchwiz variant custom ROMs to choose from, varying in different aspects of performance that you may or may not preferable to stock.
Thanks, that was a helpful reply.
If I understand you correctly, it sounds like you actually prefer the stock 5.1.1. kernel. Were you also rooted prior to the 5.1.1. update, using a custom kernel?
Rootabaga said:
Thanks, that was a helpful reply.
If I understand you correctly, it sounds like you actually prefer the stock 5.1.1. kernel. Were you also rooted prior to the 5.1.1. update, using a custom kernel?
Click to expand...
Click to collapse
I just got my 910T3 a few months ago and it already has 5.1.1 on it. I would not revert to 5.0.1 because of issues it had, like memory leaks.
And yes, I prefer stock kernel. None of the alternatives seem to match the performance or battery life of stock.