Related
Hello,
I've been flashing for a long time and currently I'm running Bionix 1.2. I've got 2 major problems and I have a workaround for each; however I thought the community might know better than me.
The first one is about the signal bars and dropped calls. I live in an area (Maine) where you never experience a dropped call since there aren't many people living. At least with my old MyTouch and stock Vibrant, I never had one. So almost once a day I drop call and see the all the signals gone. Sometimes, I see signals but there is no data or GSM connection since I cannot login to GTalk and other services (FB, twitter, etc.). I read in the development section that turning flight mode on/off can help. Well for me, it sometimes helps, sometimes doesn't. I find myself rebooting to solve the problem at least. I am a little concerned since I might need my cell in case of an emergency and I definitely would not want to wait for a reboot to call 911.
The second one is about the GPS. If I open navigation and ask for turn-by-turn directions, almost every time, it gets stuck searching for GPS. The workaround for me is to launch Maps, wait a few minutes to locate my location; then ask for directions. Although, this might not work from time to time. Again, in the middle of nowhere, you are driving and need a quick and dirty turn-by-turn directions and your smart Vibrant makes you go thru a lot of hassle to accomplish your task.
Any advice from our community?
Thank you!
Flash to stock, call t mobile and tell them your gps is non functional even after the froyo update, and get an exchange. My gps works INSTANTLY. Cold. I type my destination in Navigation and when I press enter my navigation is already talking. No maps, no 10 minutes, no downloads, we all know these are often placebos and we are still waiting and waiting for a signal which can still go off road randomly, etc. none of that with a new phone.
I did not try the physical gps fix in the forums but that could work too. Your gps still not be fixed by software, its a hardware problem. It seems phones manufactured after October (?) do not have the gps issue. Worth the hassle for me, at no cost if you do it for the gps issues and there is no physical damage to your phone. Just make sure you flash back to stock before you call because they will ask you to go through your system information on the line. Back up EVERYTHING and put it on a computer, get your exchange and flash back to your favorite rom and enjoy your now fully functional Vibrant that works in every way you bought it to work. And make sure you not only factory reset before you send the old one in, but also delete anything incriminating on your internal sd because a factory reset won't do it.
Sent from my SGH-T959 using XDA App
Don't blame the rom...Your hardware sucks.
Been running TW roms since the Bionix 1.0 days and NEVER had any issues.
Those problems are not inherent to TW roms, it's a problem with the phone.
@TheSneakerWhore, @deadpass:
OK - it might the hardware, but how do you explain no dropping calls on stock 2.1? I've used on stock for at least couple months and never had to reboot my phone because it did not have signals (or had signals but no connection).
I also flash Axura roms and never have a similar issue but they are too customized for me.
PS: I am not trying to blame the TW roms specifically nor am I defending another rom. Actually, if you open the latest Development thread, you will see my post thanking those guys because of an excellent job they've done. I am just not happy with the data and GPS - which I never had an issue before starting flashing TW and thinking others might be experiencing the same.
Strangely my GPS and cell signals seem stronger on TW ROMs than most others... It might be just slightly different hardware (not all units are created 100% equal after all) reacting differently to the software?
Have you perhaps tried Trigger v1.5? I thought the theming was very tasteful, you may like it, and it seemed pretty solid on GPS and signals.
Thanks, @Oxirane. I will give it a try.
I would try out different modems. For instance jl5 and kb1 great with gps in my case. jfd, ji6, ka5-7 all were teh suck when it came to gps. It all depends on your phone and location too. So flash away and find whats right for you.
http://forum.xda-developers.com/showthread.php?t=868774
I lol'd @ this "I live in an area (Maine) where you never experience a dropped call since there aren't many people living."
I'm with the OP on the drop call and inconsistent data issue. By all means, I have flashed almost every ROM out there. Every single ROM on here is awesome and all respects to the devs. I'm currently on Bionix 1.2 now for the third time and what I have and still noticed is the inconsistent data drop 2-3 times a day. No biggie since I managed to turn airplane off and back on and everything's back to normal. At first I thought it was KB1 that's causing this so I decided to try out different modems/kernals. After playing around a bit, I decided to stay with KA6 for a few days and noticed data improvement but still inconsistent (loss data connection). I also flashed the ROMs (Axura and Einherjar) and I don't have the data loss. I also flashed all the way back to Nero 5 just to check it out. I do not have any data problems with Nero 5. Anyways, I don't really mind every now and then switching air plane mode off/on. However, the issue as mentioned by OP does exist on some phones.
I'm running Bionix V 1.2, and the last 4 ROM's before this were all also TW ROMs.
I have not experienced a single one of your issues. My phone is fast, smooth, and have excellent signal and data everywhere around my area.
I doubt it is the ROM, but I'm no expert and cant say that for a definite.
But if myself along as many others , including a few buddies of mine, don't see those issues it just seems unlikely to be the ROM.
But who knows....
Well im guessing its the change of modems that's causing your issues... im sure it has nothing to do with the rom espeically since you never had issues supposedly when using Axura (since axura is based on bionix). Almost all the roms on here are based on TW roms, just change modems, theme, add a few random options, from what i've seen in the code. Like other suggested tryin flashing different modems and find the one that works best for your area. I've been running Bionix V 1.2 since day one and have not experienced any of the issues you have describbed...
2sh0rt said:
Well im guessing its the change of modems that's causing your issues... im sure it has nothing to do with the rom espeically since you never had issues supposedly when using Axura (since axura is based on bionix). Almost all the roms on here are based on TW roms, just change modems, theme, add a few random options, from what i've seen in the code. Like other suggested tryin flashing different modems and find the one that works best for your area. I've been running Bionix V 1.2 since day one and have not experienced any of the issues you have describbed...
Click to expand...
Click to collapse
I know your not trying to act up or anything, but thats kind of just mean.
I mean these devs are helping us by giving us more options.
Most of them aren't based on TW.
some are, most aren't.
but your saying "almost all the rom on here are based on TW Roms, just change modems, theme, add a few random options"
I'd like to see YOU edit the modem and theme and add a few random options and make a ROM. go ahead.
I can say that TW is also just editing a few codes and theming on a ROM that Samsung made, and that they aren't developers.
TW set a standard, a precedent, and people will follow it, but they aren't copying it.
not complaining at all to any ROMs. just throwing out my input to let the OP knows that he's not alone in this world. To me, if there's a way around the problem, the problem is minor. Besides, I flashed and used different ROMs like changing diapers. LOL. I like to keep my Vibrant looked different every 2-3 wks. Pretty soon, we'll see a flow of new ROMs and I be all over every single one of them like "flies on sh!t". Dang, haven't used that expression in a long time. LOL
xriderx66 said:
I know your not trying to act up or anything, but thats kind of just mean.
I mean these devs are helping us by giving us more options.
Most of them aren't based on TW.
some are, most aren't.
but your saying "almost all the rom on here are based on TW Roms, just change modems, theme, add a few random options"
I'd like to see YOU edit the modem and theme and add a few random options and make a ROM. go ahead.
I can say that TW is also just editing a few codes and theming on a ROM that Samsung made, and that they aren't developers.
TW set a standard, a precedent, and people will follow it, but they aren't copying it.
Click to expand...
Click to collapse
there is not "editing of modems" its changing modems... and theming is nothing more then changing pngs and .9s and edit xmls... its not very difficult... time consuming but not difficult. as far as what TW does to their roms in decompiling smalis and editing the Java, i've personally only seen a handful tru developers here actually doing it to what samsung has leaked. MOST of these so called roms have taken the edits that TW has done and just dropped their own changes on top of them. This has been proven time and time again! but regardless you are entitled to youre own opinions.
My point is that Axura IS based on TW's edit so if the issues persist in TW rom but not in Axura, one of the causes would most likely be due to the modem cuz im 99% sure that several Axura roms use different modems.... that is all i was trying to say.
One thing I have not seen in any of the posts that are having the issue is what modem you are using.
I will say it now, KB1 modem sucks monkey balls. I haven't had any dropped calls on it, but have stale connections all the time. What I mean by that is, my phone is sending data packets, but isn't receiving any for a good 30 seconds.
So, try a different modem. KA5 seems to be the best modem for signal and battery life.
krylon360 said:
One thing I have not seen in any of the posts that are having the issue is what modem you are using.
I will say it now, KB1 modem sucks monkey balls. I haven't had any dropped calls on it, but have stale connections all the time. What I mean by that is, my phone is sending data packets, but isn't receiving any for a good 30 seconds.
So, try a different modem. KA5 seems to be the best modem for signal and battery life.
Click to expand...
Click to collapse
THX Krylon360. To be perfectly honest, I tried different ROMs and modems and noticed some significant improvements. I totally agree that KA5 and KA6 are better for me in terms of signal hence KA6 is what I stick with as mentioned in my previous response.
surprisingly, these problems can come up from odd combos of apps or some configuration that is unique........ Lucky you
I had some phone disconnects on my phone when it was on a TW and Eugene kernel, but it was a custom mms I installed that caused the issue..... so you might look at what you got on your phone as well. Remember, some of the app developers did not or do not update their apps and this may cause an issue especially running a 2.2 platform (especially a ported 2.2 platform) if they are older apps. Food for thought
I was having the same issues with 1.2. dropped calls, no data, constantly switching from edge to 3g, etc. had no issues with nero. As everyone said, try a different modem. Worked for me.
Sent from my SGH-T959 using XDA App
Thanks everyone! krylon360, I should have mentioned the modem I've been using: KA5. So, it's weird how you and some others find KA5 and KA6 to work best and I had all these problems with it. Maybe it really is a unique combination of apps, configuration etc.
Last night I flashed KB1 and will give it a try for a few days. I tried GPS on my way to home; opened Navigation and entered directions, and I got instant lock. I see that as an improvement. Will follow closely. Thanks again!
Sent from my SGH-T959 using XDA App
There's nothing wrong with the roms i been flashing since i got my vibrant once flashing do you wait the initial 10 mins and then reboot before you start using your phone? if not you may want to try that. TW roms are pretty much flawless.
Hi guys
So we all know how to rooting wilfire, thks to AlphaRev X and others developers, but here's the question...and i've searched and i need some guidance if you please.
I dont know wich custom rom i will chose...first if its one of 2.3 (aosp or sense) or 2.2 in the same way.
By the things i've read, some have some issues like, dont have gps, wifi etc...others are not so clear what they have working and not working.
So if you could help me on this matter, would be appreciated (and others users like me would appreciated too)
Thks cheers up
You have probably read about CM, with its not working GPS and WiFi. Well, GPS works after reflashing the Radio, and, WiFi seems to have some issues with some particular channels. Changing channels helps.
Anyway, I would recommend you give a try to CM7. I have switched from Sense based ROM's, and I love the pure Android experience offered by CM7. If, after installing, you find the bugs are too hard to live by, or, Stock Android doesnt suit you (like the dialer, camera app etc.) you can always switch to a Sense based ROM, or some other. There is a lot of choice.
thks for the advise
but i did lot of reading on the forum, mostly of the failures are from the last year, hope that some had been update but i still have some reserves and i dont find any sure, about, 3G/EDGE/WIFI/GPS/CAMERA and others things even on the site wont say what will work for sure, and what might wont work....and a realy want to something with this phone, but i dont want to something that i might regret lol
Hi buddies
As Grarak chose to close the thread of his rom and that maybe some of you want to have some more return and exchanges about the way the rom works, discuss about bugs etc, i open this thread, so that we will be able to do what a forum is done for : talk and exchange together.
New version is 12082014, any return?
Testing soon..
Is calling with sim 2 in 2g working Now?
If not how to use it Any tetsters!
Edit :still No sound from sim2
and there is No way to chose network type
and No 3g from sim 2 too
Im on 9-12-14 build....2g sim not working same as official cm11....3g sim is working......
i 've had terrible battery life, and searching on google lead me to a battery misc processus eating battery, problem solved with 5.0.1 by google
do you guys have the same experience, and have heard about a fix incorporation in the new builds? :good:
I had to go all the way back to the 11-20-14 build. I tried updating to the new builds 12-8, 12-9 and 12-10. No data at all on any of these builds.
Flashed the newest build! We're on Lollipop 5.0.1 now This update is supposed to help battery life. We'll see.
The new music app automaticaly force closes, and the DSPmanager was replaced with AudioFX.
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
fabulous69 said:
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
Click to expand...
Click to collapse
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
FoxyDrew said:
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
Click to expand...
Click to collapse
mhm then i think a change that has broke the app. I m sure Grarak will correct it in the next release
Ok, the ROM was going great for me, then yesterday at work my phone turned off when it was in my pocket. I tried turning it on, it booted, started doing the boot animation and then did that for five minutes before it shut off again. This time it wouldn't turn back on no matter how many times i tried power cycling or booting into bootloader. When I got home I tried charging it and the light wouldn't even come on. So I plugged it into my PC and the phone showed up as qhsusb_bulk. After researching that i found it means the bootloader got wiped somehow. My question is, how could my bootloader be gone, because as far as I know, no one has gotten their device S-OFF.
your device is bricked
seems there is a solution on the web but not working for everybody and for specific devices
i dont know what to advice you...
i dont know if it is rom related, but if it is, i wont flash this !
Yes that's what i figured. Luckily Amazon was nice enough to give me a new phone once I send that one in. I was just trying to figure out how it would even be possible that my bootloader got fried, considering my device was still S-ON.
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
DRAGONMM2010 said:
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
Click to expand...
Click to collapse
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
Completely agreed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
fabulous69 said:
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
Click to expand...
Click to collapse
Didn't test it. Haven't spent enough time on Lollipop because of the no data issue.
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
thirteen_percent said:
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
Click to expand...
Click to collapse
Yah data works...just not good. It has to do with not being able to access APN's.
No one want's to sit "for a WHILE" to open a webpage or read an email.
On the latest build, System UI crashes.
OK, I know this is a pretty old tablet but I'd at least like to be able to get a smooth browsing, email, and streaming experience out of it; I'm not looking to be able to play games or multitask on it.
I'm running the latest version of lollipop and the N7 is rooted. Experiencing frequent serious intermittent lags/crashes, I mean like 60+ seconds can pass before the screen responds, apps hang, and the device occasionally will reboot itself. Other times, the tablet runs smoothly. Was hoping that update to lollipop would resolve some of this but, if anything, it's gotten worse. I've tried the usual "fixes" of clearing the cache, forcing TRIM, closing apps manually, and even did a factory reset + cleared all caches and still the problem persists. The problem seems to occur more frequently when I run apps like the Chrome browser, which I now avoid using. Not really sure if there is a decent process documented on how to troubleshoot these types of issues to find the root cause but the tablet is presently very annoying to use at best.
What I'd like is either: a) getting some help in determining what the root cause of the issue is, or b) switching to a ROM that doesn't have these problems.
Any thoughts, suggestions, or pointers to an in-depth troubleshooting article/thread?
If you find a solution, let me know.. I've tried combos of lollipop and kernels, kit Kat and kernels.. f2fs etc.. I keep mine as a docked alarm clock and ereader for bed.. but even that takes forever.
- Sent from Spaaaaaaaaace
I don't know if this will help, but I book marked it for when I update.
http://forum.xda-developers.com/nex...ndroid-5-0-t2999635/post58567333#post58567333
I gave up and went back to 4.4.4. I can FINALLY use my tablet again...
It's the flash memory in them. It's just degraded over time. I went back to 4.4.4 and it was excellent for about a week. Then it turned useless again.
That guide posted above seems to be a placebo other than the animation's being turned off. The n7 is absolutely fine after a fresh wipe, or a factory reset. For a week... I went through the guide and the only things it had that would make a real difference was animation speeds. I'll see how it does in a week.
- Sent from Spaaaaaaaaace
hi! I was having the same problem, my n7 was super laggy and sometimes rebooted itself. that was just after uprading to lollipop 5.0.2. it kinda solved after rooting, doing a factory reset and installing lollipop 5.1. I hope it helps!
4.4.4 stock with all-f2fs rom. M-kernel r69. Both can be found here on xda.
This is how I got mine running smoothly again, even after trying several lollipop roms including 5.1.
Sent from my Nexus 7 using XDA Free mobile app
CM12 is not doing any better, I hope 5.1 could make a difference.
Stock 5.1 + Franco kernel with /data and /cache formatted to f2fs works beautifully for me. No problems at all.
I had all the same problems (and more) you and other spoke about when (a structure that holds back water and sounds like Ham) Google hounded and hounded me to install LolliCrap 5.02 (I ignored 5.0, which somehow disappeared). I HATED my #1 Nexus 7 16GB v2012. I also have a #2 Nexus 7 32GB v2012 (running HAPPILY 4.4.4) which I am still ignoring for "ham" good reason to install 5.02, an I never will install it or the latest 5.1!!
I have been exploring reinstalling the stock 4.4.4, but first I want know how to turn OFF future Google OEM Android updates and stop the "ham" badgering that there is a "new update available. But in the mean time, want to make #1 N7 useful again, I bite the bullet, backed up everything and did a factory reset and reinstalled everything. Even though I still HATE LolliCrap, my #1 N7 16GB is running pretty snappy again though some apps absolutely DON'T LIKE LolliCrap OS and are hanging and hanging and slow and crash (lazy Devs that aren't fixing whatever is causing that with 5.x). Apps I've noticed that are horribly slow with 5.x are Outlook, Skype, Yahoo Mail, Weather Underground, Drop Box, others
So, do a full reset and reinstall after backing up your data. You're gonna lose everything anyway when you Root and Boot Unlock to install an older version of Android or a custom ROM.
Hope this helps.
Glad to see another post here on the very topic I'm looking for. I'm currently running stock 5.1, completely stock, and it's just as bad as 5.0 was. I've read up enough to realize the issue is a flaw with the device, but am going to try and devote an evening or 3 to making this thing work before I completely give up on it. My goal is a minimal, feature poor but reasonably fast device for browsing, email, and some specific apps (a game or 2 and the Harmony Remote app)
Below are the areas I'm looking at, if anyone has advice or tips on any of these I'd really appreciate it:
Custom Kernel- Franco or MKernel r69? Need to investigate
F2FS - This is probably the best shot
Custom ROM - May stay stock, but if anyone knows of a lean, limited feature bloat ROM let me know!
Lightweight Browser - Can we get the original "Browser" App to install? Other options?
Basic EMail Client - not sure about this one..
The moment I saw the thread title, I knew I was not alone on this.
I remember the behavior first started with 4.4.4 actually, refusing to turn the screen on sometimes etc. I tried CM12+f2fs+mkernel 69 and it went well for a few days, then stuff broke again. I first suspected it's a RAM issue because I have two users running, but it constantly has about 150-200MB free (counting the cached apps, 400+ otherwise).
I guess I'll try slimkat 4.4.4 + f2fs modification, hope it can get the tablet running again.
Reapman said:
Glad to see another post here on the very topic I'm looking for. I'm currently running stock 5.1, completely stock, and it's just as bad as 5.0 was. I've read up enough to realize the issue is a flaw with the device, but am going to try and devote an evening or 3 to making this thing work before I completely give up on it. My goal is a minimal, feature poor but reasonably fast device for browsing, email, and some specific apps (a game or 2 and the Harmony Remote app)
Below are the areas I'm looking at, if anyone has advice or tips on any of these I'd really appreciate it:
Custom Kernel- Franco or MKernel r69? Need to investigate
F2FS - This is probably the best shot
Custom ROM - May stay stock, but if anyone knows of a lean, limited feature bloat ROM let me know!
Lightweight Browser - Can we get the original "Browser" App to install? Other options?
Basic EMail Client - not sure about this one..
Click to expand...
Click to collapse
1. For some reason Franco never boot my tablet for me...I've been using mkernel r69 and that's working really well.
2. Yep, a must.
3. Tried several custom roms and came back to stock.
4. Opera
5. Stock email, the one can be downloaded via playstore?
Rastapop with Franco kernel runs great to me. Keeping this thing alive.
VintageGuitarz said:
[...] I have been exploring reinstalling the stock 4.4.4, but first I want know how to turn OFF future Google OEM Android updates and stop the "ham" badgering that there is a "new update available [...]
Click to expand...
Click to collapse
To remove the update questions you got to root the device and disable the SystemUpdateService service of Google Service Framework and Google Play Services applications (don't know, maybe only Play Service one is really required, but better block both of them).
To do that use this application http://play.google.com/store/apps/details?id=cn.wq.disableservice
Reapman said:
Glad to see another post here on the very topic I'm looking for. I'm currently running stock 5.1, completely stock, and it's just as bad as 5.0 was. I've read up enough to realize the issue is a flaw with the device, but am going to try and devote an evening or 3 to making this thing work before I completely give up on it. My goal is a minimal, feature poor but reasonably fast device for browsing, email, and some specific apps (a game or 2 and the Harmony Remote app)
Below are the areas I'm looking at, if anyone has advice or tips on any of these I'd really appreciate it:
Custom Kernel- Franco or MKernel r69? Need to investigate
F2FS - This is probably the best shot
Custom ROM - May stay stock, but if anyone knows of a lean, limited feature bloat ROM let me know!
Lightweight Browser - Can we get the original "Browser" App to install? Other options?
Basic EMail Client - not sure about this one..
Click to expand...
Click to collapse
In my experience best custom ROM is Resurrection Remix.. I tried all tilapia Lolllipop ones except AICP, which now I'm very curious to try.. but I flashed Paranoid Android 4.6 BETA 6 yesterday and I will not change it until Google releases 5.1 firmware for tilapia too and people say this build is finally smooth and nice (well, too much hope, I know.. Lollipop will never be smooth on Nexus 7 2012, I fear )
Sofar I'm about 24 hours in using SlimKat with F2F2 (followed this post here - http://forum.xda-developers.com/showthread.php?t=2678142) using "Browser" that it comes with, and so far just GMail. Initial findings are very positive, it's quite fast, but I'm sure that could change.
Next steps (thanks for the ideas all!):
Install Opera
There's actually an update to SlimKat, but i'm waiting to see how the tablet performs as is without touching anything
Install and configure EMail client from Play store
Kernel - looks like this version of SK already uses the M Kernel so should be good there
There is an updated, F2FS modified version of Slimkat in that thread around page 90 or something.
I'm using that at the moment and it's been fine I guess.
Word of warning: recents menu is bugged to secondary user acounts. Only shows apps if they have been also installed for the primary user.
Yeah, I'm going to give myself a week or so on this older build and make sure it's stable before doing that. Definitely some stuff I miss from Lollipop in this, but if this is enough to breath new life into the tablet.. I'm willing to accept that loss :good:
Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.
If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.
DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads
Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.