Database Users

[Q][I9505]What breaks wifi and why in custom roms?

Over in the Omega thread for the I9505, I've been having a discussion with a few people regarding why the wifi breaks when you flash say an MF4 based rom from an older base (like if you're on stock MEA or something) however all I got in response was to flash an MF4 modem package and wifi will start working.
Wifi, as we all know, is handled by the kernel and not the modem, so why does wifi start working when you flash the modem for the base you're on if you're using a stock kernel? Are the stock kernels dependent of a certain modem? Because when I flashed Wanam's Adam kernel (source-built) straight over Omega 6 (MF4), wifi started working.
Why is it like this, you think?
http://forum.xda-developers.com/showpost.php?p=42806026&postcount=4104

Theshawty said:
Over in the Omega thread for the I9505, I've been having a discussion with a few people regarding why the wifi breaks when you flash say an MF4 based rom from an older base (like if you're on stock MEA or something) however all I got in response was to flash an MF4 modem package and wifi will start working.
Wifi, as we all know, is handled by the kernel and not the modem, so why does wifi start working when you flash the modem for the base you're on if you're using a stock kernel? Are the stock kernels dependent of a certain modem? Because when I flashed Wanam's Adam kernel (source-built) straight over Omega 6 (MF4), wifi started working.
Why is it like this, you think?
Click to expand...
Click to collapse
Ya even though the WiFi module is in the kernel it would seem that Samsung have put some sort of dependency in there that relies on a particular modem. (Maybe it is just that particular modem and all other modems from the MF4 one on will work with whatever new kernel you use, it could just be something big they changed in MF4 compared to MEA)
Sent from my Nexus 7 using Tapatalk 4 Beta

nodstuff said:
Ya even though the WiFi module is in the kernel it would seem that Samsung have put some sort of dependency in there that relies on a particular modem. (Maybe it is just that particular modem and all other modems from the MF4 one on will work with whatever new kernel you use, it could just be something big they changed in MF4 compared to MEA)
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
From what I can gather, it's always been like this. Check this thread (last pages) and see that they are being highly ignorant. http://forum.xda-developers.com/showthread.php?t=2253528&page=410
It's basically this: "flash the latest modem or sod off" but used with kinder words. I refuse to flash the MF4 modem just to fix the wifi when I know that flashing a source-built kernel fixes it just as well. Besides, a newer modem doesn't mean a better modem. The problem needs to be fixed, not circumvented.

Don't forget that people do stupid things just because they have heard that's what to do, need I mention the 'calibrating' the battery situation! If you can get it working with a custom kernel built from source then that is the way it should be done as it isn't a modem issue, it is a kernel issue, obviously Sammy put something in there that changed how it works in the last code drop.
On the other hand, maybe they did that to force people to use only the new modem, maybe the old one uses too much power, has bugs etc. God only knows why they do what they do.
Sent from my Nexus 7 using Tapatalk 4 Beta

nodstuff said:
Don't forget that people do stupid things just because they have heard that's what to do, need I mention the 'calibrating' the battery situation! If you can get it working with a custom kernel built from source then that is the way it should be done as it isn't a modem issue, it is a kernel issue, obviously Sammy put something in there that changed how it works in the last code drop.
On the other hand, maybe they did that to force people to use only the new modem, maybe the old one uses too much power, has bugs etc. God only knows why they do what they do.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think we'd need the help of some very experienced kernel devs. Maybe @AndreiLux can share his knowledge?

That's probably the best option, get a definitive answer from someone that understands this stuff better than we do.
Sent from my Nexus 7 using Tapatalk 4 Beta

nodstuff said:
That's probably the best option, get a definitive answer from someone that understands this stuff better than we do.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I bet Samsung has placed some sort of dependency in the kernel (like you said) that when it doesn't find the right modem, it crap out and destroys wifi.
Djembey had an interesting reply: http://forum.xda-developers.com/showpost.php?p=42806026&postcount=4104

Thread closed at OP's request.

Kernels For I337M?

Hey guys. So i've been beating my head against the wall here, trying to search ( yes as in using google and the xda search ) for a solution.
I keep trying to flash stock based samsung roms, they would flash, but when i try to open the camera, it opens but it freezes and then comes back saying camera failed. So I wait about 10 minutes, and the camera works...but only for about a minute, then it freezes and then never opens again.
I've tried flashing all of faux123 kernels, only one worked ( 006-MDX ) but the camera still has issues and I can't seem to find any other kernels compatible with the I337M.
Anyways, I've now tried flashing a I337M firmware based custom rom and it boots but now there it just wont boot up at all, just gets to the samsung logo and sits there, I've tried flashing other kernels but nothing will help. I'm going to have to Odin back to stock, but I'm wondering what Kernels are ok to use with the I337M so that this doesn't happen to me again in the future.
Any help and I'll have my thanks finger ready
EDIT: Ok, so after some poking around, it seems that T-Mobile kernels work well with the I337M. Can anyone confirm this for me before I bork my device again? (currently doing an odin back to stock and re-rooting... =(

It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.

TheSmokingAndroid said:
Hey guys. So i've been beating my head against the wall here, trying to search ( yes as in using google and the xda search ) for a solution.
I keep trying to flash stock based samsung roms, they would flash, but when i try to open the camera, it opens but it freezes and then comes back saying camera failed. So I wait about 10 minutes, and the camera works...but only for about a minute, then it freezes and then never opens again.
I've tried flashing all of faux123 kernels, only one worked ( 006-MDX ) but the camera still has issues and I can't seem to find any other kernels compatible with the I337M.
Anyways, I've now tried flashing a I337M firmware based custom rom and it boots but now there it just wont boot up at all, just gets to the samsung logo and sits there, I've tried flashing other kernels but nothing will help. I'm going to have to Odin back to stock, but I'm wondering what Kernels are ok to use with the I337M so that this doesn't happen to me again in the future.
Any help and I'll have my thanks finger ready
EDIT: Ok, so after some poking around, it seems that T-Mobile kernels work well with the I337M. Can anyone confirm this for me before I bork my device again? (currently doing an odin back to stock and re-rooting... =(
Click to expand...
Click to collapse
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.

blyndfyre said:
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.
Click to expand...
Click to collapse
Ya, I've done the whole adam kernel in the past, updated the camera firmware, everything was fine, but this time around, the firmware didn't need updating, at least i don't think so, considering the camera app launches, but sits at a black screen and then gives me a message that camera failed. it never tries to update the firmware like it did in the past. thanks though =)
TheAxman said:
It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.
Click to expand...
Click to collapse
Ya, I have been trying the correct firmwares for my device and nothing seems to fix it, thanks though

TheAxman said:
It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.
Click to expand...
Click to collapse
Most of the AT&T kernels are Loki :s... with a custom recovery that auto Loki I don't understand why to Loki a Rom... besides making it only for AT&T :s
I have a stock kernel that I backed up with twrp... the rest are T-Mobile
Sent from my i337M

blyndfyre said:
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.
Click to expand...
Click to collapse
Wait, on the unlocked bootloader devices, you mean the other carriers kernels is ok to flash? man, I seriously wish our att was unlocked, this is good to know thanks.
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
TheSmokingAndroid said:
Ya, I've done the whole adam kernel in the past, updated the camera firmware, everything was fine, but this time around, the firmware didn't need updating, at least i don't think so, considering the camera app launches, but sits at a black screen and then gives me a message that camera failed. it never tries to update the firmware like it did in the past. thanks though =)
Ya, I have been trying the correct firmwares for my device and nothing seems to fix it, thanks though
Click to expand...
Click to collapse
I stand corrected, your device from the post earlier says you can use other kernels. what a concept.

TheAxman said:
Wait, on the unlocked bootloader devices, you mean the other carriers kernels is ok to flash? man, I seriously wish our att was unlocked, this is good to know thanks.
Click to expand...
Click to collapse
Yeah us SGH-I337M users can use other device ROM's and Kenels. (Doubt not the 9500 because of hardware differences)
We pay for our unlocked bootloader in outrageous plans from our mobile providers though!

im in winnipeg here on the i337m rogers and have no problem with the kernal in my signature

blyndfyre said:
Yeah us SGH-I337M users can use other device ROM's and Kenels. (Doubt not the 9500 because of hardware differences)
We pay for our unlocked bootloader in outrageous plans from out mobile providers though!
Click to expand...
Click to collapse
I can imagine, I still have a g3 that is in working order with a sim, and it is cool to see the loader unlocked. although on the g4, as long as I can flash a rom, I do not care how it works. I am a happy camper right now.
Thanks for clearing up the kernel question I had, can use that info when helping others. Thanks.

TheAxman said:
I can imagine, I still have a g3 that is in working order with a sim, and it is cool to see the loader unlocked. although on the g4, as long as I can flash a rom, I do not care how it works. I am a happy camper right now.
Thanks for clearing up the kernel question I had, can use that info when helping others. Thanks.
Click to expand...
Click to collapse
I guess with LOKI you are still set, the biggest drawback with the locked bootloader is probably slower device reboots, as you see the custom screen?
Your welcome about the kernel question I always see you helping others. Fell free to toss me a thanks.

blyndfyre said:
I guess with LOKI you are still set, the biggest drawback with the locked bootloader is probably slower device reboots, as you see the custom screen?
Your welcome about the kernel question I always see you helping others. Fell free to toss me a thanks.
Click to expand...
Click to collapse
I have no problem on the thanks, but I have none left today, you and another killed em up...I will catch you though.
Thanks, here, and 1 a coming.

Could somebody please share a link to download Rogers/Fido stock kernel (rooted or not rooted) for i337M please ?
Thanks!

fmark said:
Could somebody please share a link to download Rogers/Fido stock kernel (rooted or not rooted) for i337M please ?
Thanks!
Click to expand...
Click to collapse
Thread containing Canadian SGH-i337m stock firmware and kernels:
http://forum.xda-developers.com/showthread.php?t=2269304
Link to Rogers kernel:
http://hotfile.com/dl/215149326/c15...GH-I337M-RWC-I337MVLUAMDJ-1366643831.tar.html

When waking up device, gets black screen, hangs for few secs, then reboots

When attempting to wake up device (SPH-L720) from sleep using power or home button, it doesn't wake up, gets blank screen, the menu and back soft buttons LED lights come on, hangs for few secs on the black screen, then reboots by itself. Issue happens randomly and sometimes once a day or multiple times an hour. It seems like the problem existed before rooting and installing custom ROM but I've just noticed it.
I'm using TriForce 3.0 ROM (Android 4.2.2) w/ baseband L720VPUAMDL and kernel 3.4.0-KT-SGS4-ga23d84c. I've tried wiping/reinstall ROM, reflashing back stock ROM, removing microSD card. Nothing helped. The battery charges properly and is usually fully charged. No wear and tear or damage of any kind. Device is 1 month old.
Any ideas what might be causing the problem and suggestions for possible fix?

its because of the kernal, mine does this aswell..

kyledb said:
its because of the kernal, mine does this aswell..
Click to expand...
Click to collapse
Did you find a fix? Does changing the kernel fix the problem? If so, which kernel did you go with? It's driving me crazy lol. Thanks!

I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.

beerindex said:
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
Click to expand...
Click to collapse
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.

verto8 said:
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
Click to expand...
Click to collapse
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.

I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying

There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading

beerindex said:
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
Click to expand...
Click to collapse
Same situation here. I rooted and flash a custom ROM on mine right after I got it. I believe it had the issue pre-root on stock ROM/kernel, but I'm not a 100% sure. I had same issue w/ the Cyanogenmod ROM, not sure what kernel it was using.
kyledb said:
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
Click to expand...
Click to collapse
Do you remember if you had the issue on stock ROM before rooting? I believe mine has always existed and might be a hardware problem because I tried different ROMs/kernels and issue persisted with all of them.
ParkerParker said:
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
Click to expand...
Click to collapse
Is there a comparison thread of different kernels? I'm wondering what the pros/cons of each and maybe some user experience feedback. I believe mine was rebooting as well when it was on stock before rooting. This seems like it might be a hardware problem rather than software (ROM/kernel). Do you think everyone w/ a Sprint Galaxy S4 (SPH-L720) is having this issue? If so, Samsung should do something about it because it's super annoying!

Update: I've been using latest version of KT-SGS4 kernel 3.4.59 (Aug 25 build) for over a day and it's been pretty stable w/ no occurrence of the problem. I'll keep this thread posted w/ updates if I run into any problem. Thanks to everyone for their help!
2nd Update: it still has the problem.

It's still happening but at a slightly lower frequency with the latest KT-SGS4 kernel. For those who have tried a different kernel, did it fix the problem? I'm trying to narrow down the source and convince myself for certain that it's a software rather than a hardware issue.

Same issues
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.

grnerd said:
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
Click to expand...
Click to collapse
Try that and odin back to stock mf9 not mdl. Tri-force is mf9 based so maybe thats why you get those issues because you need firmware kernel modem and such. Also it could be that kt kernel had been reported to cause some of those issues.

i went to a new rom and new kernal and this is still happening to me, i have no idea what it is now.... any solutions from anyone?
UPDATE: BAD MICRO SD CARD!!!!!!!!!!! REMOVED MY SD CARD AND NO ISSUES IN THE PAST 2 DAYS
NEW UPDATE: SPOKE TO SOON..

Does 9505 Roms work on S4 Value Edition? (9515)

Hi guys, i'm planning to buy an Galaxy S4 Value Edition Model 9515L (L from Latin, probably southamerican-friendly frequencies) (The only difference i guess is the back cover and it comes with 4.4) and i want to know if i can install S4 9505 ROMS on it, is there any problem? Plus, is there also a root for it?

No, you can't flash those roms.

What actually is the difference between a regular S4 and a 'Value' S4. pdadb.net shows they have pretty much identical specs?!

dave106 said:
What actually is the difference between a regular S4 and a 'Value' S4. pdadb.net shows they have pretty much identical specs?!
Click to expand...
Click to collapse
I guess it's the basebands and software

Lennyz1988 said:
No, you can't flash those roms.
Click to expand...
Click to collapse
even if the hardware is the same? There are alot of unified ROMs for several défices, isnt there ANY way of converting ROMS to work on value edition? Or at least its possible to root the phone?

I believe that the ROMs may work since the unified builds work, however does it have LTE?
Sent from my GT-I9505 using XDA Premium 4 mobile app

Battlehero said:
I believe that the ROMs may work since the unified builds work, however does it have LTE?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, its the SAME hardware as the Galaxy S4 LTE, the only difference is that it comes with 4.4 instead of 4.2.2

Root I9515 with CF-Autoroot file for I9505
EverLost123 said:
even if the hardware is the same? There are alot of unified ROMs for several défices, isnt there ANY way of converting ROMS to work on value edition? Or at least its possible to root the phone?
Click to expand...
Click to collapse
I just rooted my I9515 with the I9505 CF-Autoroot file. :good: It all ran quick and easy, as if they really were the same phone. Haven't tried any customs roms yet, so I can't say anything about them. The rooting, although, is flawless so far.

Rune Walker said:
I just rooted my I9515 with the I9505 CF-Autoroot file. :good: It all ran quick and easy, as if they really were the same phone. Haven't tried any customs roms yet, so I can't say anything about them. The rooting, although, is flawless so far.
Click to expand...
Click to collapse
so, if root works, everything that you flash that is not a ROM that is supposed to work on 9505 will work on 9515?

EverLost123 said:
so, if root works, everything that you flash that is not a ROM that is supposed to work on 9505 will work on 9515?
Click to expand...
Click to collapse
I'd be very cautious on jumping to that general conclusion.
Although the CF-Autoroot for I9505 has worked in my device, when I flashed the I9505 TWRP (2.7), I couldn't use it because the touch screen didn't work. Then I tried I9505 CWM (6.0.4.7, non-tocuh), and everything was smooth and functional.
Later, I flashed Slimkat 5 (which is supposed to be S4 LTE unified, I9505 included, but obviously not for the I9515 yet), but the touch hasn't responded as well. After a few minutes being really afraid I'd burned the digitizer for good :crying:, I was able to flash the stock I9515 rom and the touch went back to life! :victory:
So, it seems that flashing I9505 stuff (even custom roms) in the I9515 is possible, but the touch doesn't work. That is just a first impression based in my quick experience in this matter, though.

Rune Walker said:
I'd be very cautious on jumping to that general conclusion.
Although the CF-Autoroot for I9505 has worked in my device, when I flashed the I9505 TWRP (2.7), I couldn't use it because the touch screen didn't work. Then I tried I9505 CWM (6.0.4.7, non-tocuh), and everything was smooth and functional.
Later, I flashed Slimkat 5 (which is supposed to be S4 LTE unified, I9505 included, but obviously not for the I9515 yet), but the touch hasn't responded as well. After a few minutes being really afraid I'd burned the digitizer for good :crying:, I was able to flash the stock I9515 rom and the touch went back to life! :victory:
So, it seems that flashing I9505 stuff (even custom roms) in the I9515 is possible, but the touch doesn't work. That is just a first impression based in my quick experience in this matter, though.
Click to expand...
Click to collapse
This times a thousand!
It's totally plausible that the 9505 is completely interchangable with the 9515.
It's also totally plausible that flashing a 9505 recovery on the 9515 will brick it beyond all repair.
And then its plausible that some things are compatible but others aren't without any pattern to figure it out by. (CWM Recovery might be fine but TWRP might brick it, etc)
It's your phone so you can do whatever you want. Lord knows that the vast majority of hacks to gain root (and various other things) have been tested by someone manning up and just rolling the dice on their phone to see if it works or bricks it. So feel free to try it, but be very careful, research first, and know that nothing is guarenteed until AFTER it flashed successfully and boots.

Skipjacks said:
This times a thousand!
It's totally plausible that the 9505 is completely interchangable with the 9515.
It's also totally plausible that flashing a 9505 recovery on the 9515 will brick it beyond all repair.
And then its plausible that some things are compatible but others aren't without any pattern to figure it out by. (CWM Recovery might be fine but TWRP might brick it, etc)
It's your phone so you can do whatever you want. Lord knows that the vast majority of hacks to gain root (and various other things) have been tested by someone manning up and just rolling the dice on their phone to see if it works or bricks it. So feel free to try it, but be very careful, research first, and know that nothing is guarenteed until AFTER it flashed successfully and boots.
Click to expand...
Click to collapse
That is absolutely true!
There is at least one legitimate reason for devices being sold without straight forward root access: consumers safety, that is, avoiding them to brick their devices tweaking something they don't fully know or understand. That way, granting root access is a risk itself, and the ones which decide to do it should be aware of those risks (and be responsible for the consequences). And, if using a rooting procedure to your specific device is a risk itself, trying stuff for a different (albeit similar) one is a risk even bigger!
In my case, I ended up with a european phone I can't use in Brazil, what made me try and unlock it by all means, including the very risky ones. And, even though I'm far from having any deep linux/android knowledge, I know exactly the risks of what I'm doing, and things are really like giving stuff a try and rolling the dice.
That is the experience I'm sharing in this thread, but, like Skipjacks advised, be very careful before trying anything - and, when you do, be aware of the risks involved.

Rune Walker said:
I'd be very cautious on jumping to that general conclusion.
Although the CF-Autoroot for I9505 has worked in my device, when I flashed the I9505 TWRP (2.7), I couldn't use it because the touch screen didn't work. Then I tried I9505 CWM (6.0.4.7, non-tocuh), and everything was smooth and functional.
Later, I flashed Slimkat 5 (which is supposed to be S4 LTE unified, I9505 included, but obviously not for the I9515 yet), but the touch hasn't responded as well. After a few minutes being really afraid I'd burned the digitizer for good :crying:, I was able to flash the stock I9515 rom and the touch went back to life! :victory:
So, it seems that flashing I9505 stuff (even custom roms) in the I9515 is possible, but the touch doesn't work. That is just a first impression based in my quick experience in this matter, though.
Click to expand...
Click to collapse
Hm... So, there are touchscreen drivers for each ROM(device) right? So if devs make ROMS with 9515 drivers maybe we could get it working?
I really can't understand that... the phone is almost exact like the original S4. EVERY spec besides frequencies, why there is so much difference?

EverLost123 said:
Hm... So, there are touchscreen drivers for each ROM(device) right? So if devs make ROMS with 9515 drivers maybe we could get it working?
I really can't understand that... the phone is almost exact like the original S4. EVERY spec besides frequencies, why there is so much difference?
Click to expand...
Click to collapse
I'd love to see xda experts developing I9515 stuff, for I'm sure they would work just fine, but I'm afraid this might not happen. This S4 version is kind of a last selling one, and, with the new devices coming out, devs may not be interested in working in a dated - and probably not so spread - version.
Regarding the specs, I do think that, if we could flash the hole I9505 software, and not only a main kernel file, maybe we could get everything working. Nevertheless, I don't know where to get those files, nor how I could do that through Odin, or even how to bypass the write protection enabled bootloader.

Rune Walker said:
I'd love to see xda experts developing I9515 stuff, for I'm sure they would work just fine, but I'm afraid this might not happen. This S4 version is kind of a last selling one, and, with the new devices coming out, devs may not be interested in working in a dated - and probably not so spread - version.
Regarding the specs, I do think that, if we could flash the hole I9505 software, and not only a main kernel file, maybe we could get everything working. Nevertheless, I don't know where to get those files, nor how I could do that through Odin, or even how to bypass the write protection enabled bootloader.
Click to expand...
Click to collapse
I would love to hear what most devs have to say about this

We need xda devs help!
EverLost123 said:
I would love to hear what most devs have to say about this
Click to expand...
Click to collapse
So would I...
Today I tried a different 9505 ROM (Omega v31) in my 9515. Just like the other time, the installation went ok (albeit tough to go through, because AROMA didn't respond to touch), but, after the device rebooted, I couldn't get the touch screen to work as well. Adding this new experience to the previous ones, I think it's reasonable to state that, at least so far, the main incompatibility regarding the 9505 and the 9515 is the touch screen drivers...
Could any dev help us out here? Any possibility of custom recovery and roms for the I9515?

Hey there!! I don' t have an s4 anymore and i guess this is basically the reason you don' t see any custom rom for s4VE.. all has a 9505 or an s5 now..
Anyway.. when i had the s4 i tried to build a rom for the 9515 and sent to a tester.. unfortunately it didn' t boot.. so i guess it was due yo the kernel.. so i thought.. why not to flash the single system and leave the stock, altready rooted kernel?.. and believe me i would have bet my car it should have worked.. but it didn' t ?? even if the same rom worked as a charme on my s4 with 9505 kernel modules.. ?
So to @Rune Walker if you' re up for a test i would really love to have a second attempt, given that you already know and tested how to recover... so i will PM you soon ?

Wuby986 said:
Hey there!! I don' t have an s4 anymore and i guess this is basically the reason you don' t see any custom rom for s4VE.. all has a 9505 or an s5 now..
Anyway.. when i had the s4 i tried to build a rom for the 9515 and sent to a tester.. unfortunately it didn' t boot.. so i guess it was due yo the kernel.. so i thought.. why not to flash the single system and leave the stock, altready rooted kernel?.. and believe me i would have bet my car it should have worked.. but it didn' t ?? even if the same rom worked as a charme on my s4 with 9505 kernel modules.. ?
So to @Rune Walker if you' re up for a test i would really love to have a second attempt, given that you already know and tested how to recover... so i will PM you soon ?
Click to expand...
Click to collapse
I'll be looking forward to run the test! :good:

Wuby986 said:
Hey there!! I don' t have an s4 anymore and i guess this is basically the reason you don' t see any custom rom for s4VE.. all has a 9505 or an s5 now..
Anyway.. when i had the s4 i tried to build a rom for the 9515 and sent to a tester.. unfortunately it didn' t boot.. so i guess it was due yo the kernel.. so i thought.. why not to flash the single system and leave the stock, altready rooted kernel?.. and believe me i would have bet my car it should have worked.. but it didn' t ?? even if the same rom worked as a charme on my s4 with 9505 kernel modules.. ?
So to @Rune Walker if you' re up for a test i would really love to have a second attempt, given that you already know and tested how to recover... so i will PM you soon ?
Click to expand...
Click to collapse
hey there, I also have a 9515 and know how to recover, even PM`d Rune Walker for more info on this, so if you need an extra tester hit me up

righi said:
hey there, I also have a 9515 and know how to recover, even PM`d Rune Walker for more info on this, so if you need an extra tester hit me up
Click to expand...
Click to collapse
thanks.. in the past days i wasn't able to think to anything new.. the rom is working with no wifi by now.. so i guess is not ready to release.. i was actually thinking to make a "patch" in order to make the 9505 rom working with the V.Ed.. but is still a project, and nothing more
thanks for your help, i will consider if need!

[H918] Random Reboots on Custom Roms

So, I had a day 1 v20 that began randomly rebooting back in december. Thought it was a hardware issue and finally got around to replacing it the other day. Now, after getting the replacement v20 set up on a custom rom (AICP) I'm seeing random reboots again. I've tried every single custom rom available for the h918 and they all experience reboots. When i've asked about the issue in the threads it seems as if I'm the only one. It appears to be a custom-rom only problem that apparently no one else is experiencing? The kernel panics are being caused by the modem, and it started happening when I upgraded to the 10j base. This replacement also came with 10j. Am I just super unlucky with two duds or is there really something going on here?
TLDR; Anyone else with a h918 with 10j bootloader/modem running custom roms and seeing random reboots?

What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.

Biff627 said:
What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.
Click to expand...
Click to collapse
Have always left kernel stock.

Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???

Biff627 said:
Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???
Click to expand...
Click to collapse
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.

trobertson said:
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.
Click to expand...
Click to collapse
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.

Biff627 said:
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.
Click to expand...
Click to collapse
The phone came with stock 10j.. flashing this wouldn't change anything.

trobertson said:
The phone came with stock 10j.. flashing this wouldn't change anything.
Click to expand...
Click to collapse
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there

Biff627 said:
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there
Click to expand...
Click to collapse
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc

trobertson said:
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc
Click to expand...
Click to collapse
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?

Biff627 said:
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?
Click to expand...
Click to collapse
Aicp, rr, cm-remix, stock Lineage.

trobertson said:
Aicp, rr, cm-remix, stock Lineage.
Click to expand...
Click to collapse
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom

Biff627 said:
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom
Click to expand...
Click to collapse
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j as most custom ROM users are still running 10d firmware

trobertson said:
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j
Click to expand...
Click to collapse
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.

Biff627 said:
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.
Click to expand...
Click to collapse
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.

trobertson said:
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.
Click to expand...
Click to collapse
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents

Biff627 said:
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents
Click to expand...
Click to collapse
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.

trobertson said:
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.
Click to expand...
Click to collapse
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya

Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
Not a Samsung fan. Especially with KNOX. I buy phones first based on the chances of development producing workable custom ROMs and second based on hardware features.
Back to the main topic: I just managed to flash the 10i modem alone so we'll see what happens. I'm working on extracting the 10d modem as well.

Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
UPDATE: Flashing the 10i modem made no difference, still having random reboots (although they seem less frequent), I will try the 10d modem once I find a way to extract it from the TOT files posted on this forum.