Infuse Kernel Dev - Samsung Infuse 4G

I have just recently gotten into flashing my phone and learning more about how the Android system works on the back end. I am fairly new to Linux and haven't used it much, just some minor support at work. I have asked a couple of questions in these forums but haven't really gotten any responses, I think I'm just not asking the right questions.
I have been researching some issues on these forums and on the web that I am seeing with my phone, and it sounds like other people may be seeing. When the UCKK2 leak came out from Samsung last month, in my ignorance I went ahead and flashed the leak without waiting for any dev work to be done to it. In doing that, I ended up flashing the bootloader for gingerbread to my phone. As far as I know, since then I have had an issue where the proximity sensor on my phone doesn't work. I ended up calling AT&T tech support, and they had me put in a code, can't remember what it was, for some device diagnostics. I was able to activate the proximity sensor and it was showing input, but it wasn't affecting the phone at all. I am thinking that there is an incompatibility between the gingerbread bootloaders and the custom kernels that are currently out for the Infuse. Am I way off base on this? I believe the Proximity Sensor wasn't even working for the stock kernel.
I know Linux and Entropy are the main kernel devs for our system but I was really hoping to be able to learn more about kernel compiling so I could begin to help out with this. I have compiled a couple of kernels for desktop versions of linux, so I have gotten my hands somewhat dirty.
Thanks for everything that everyone does on this site Hopefully I can get to the point where I can contribute more.

Proximity sensor is working well and good on mine - since stock to custom froyo to custom GB roms, including Roger's based GB rom that I am on now.

Any diagnostic you ran had to talk to the kernel driver to get that data, so it isn't necessarily a kernel issue, but more than likely, a framework issue. Now, when I say this, take it with a grain of salt. It could very well be that the framework is expecting a different FORMAT for the data that the kernel is not providing at this time. So an updated driver in the kernel could very output things in a way that the newer framework is expecting. Regardless, it doesn't have anything to do with the bootloaders either way. Now, assuming that the stock kernel from these leaks works, then you've just discounted the kernel -> framework issue entirely, and it becomes entirely an issue with the framework, unless Samsung screwed up their own kernel as well.

Ok, I wasn't sure how much play the bootloaders had in the actual running of the operating system, but from what you say Linux, that makes sense. If I have time tonight I will go ahead and flash a stock UCKL2 leak to my phone and see if that has any effect on the issue. I have been using code *#*#0588#*#* to test the proximity sensor on Samsung roms, don't know if that one is any good though. it will load up what looks like a proximity sensor test, but I don't know how it's supposed to work. I have been running CM7 for about a week and the Proximity Sensor has been dead that entire time, plus a couple of other Gingerbread ROMs before that.

So you are saying that when in a phone call, and you hold your phone up to your ear, the screen doesn't shut off?

Correct, the screen will automatically shut off after the 30 second delay time, so when I pull the phone away from my ear I have to hit the power button to get the screen back on.

Prox sensor failures are usually caused by a bogus screen protector.
Plenty of people are running KL2 without any prox sensor issues.

Ok, guess my phone is defective then, I'll have to get it taken care of. I am interested in learning about compiling kernels for android, where would be a good place to start learning to do that?

skelleyton said:
Ok, guess my phone is defective then, I'll have to get it taken care of. I am interested in learning about compiling kernels for android, where would be a good place to start learning to do that?
Click to expand...
Click to collapse
I think its ur Phone issue as u mentioned... But try using Pure stock..with this changes in build.prop. I never tried it. but might work.
Disable black screen issue after call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Source for above tweak: http://forum.xda-developers.com/showthread.php?t=1331351

Related

[Warning] Don't Flash Kernels for Other Hardware!!..

I know it may be tempting to flash Fascinate or Showcase (or Vibrant, or i9000, etc) ROMs and Kernels especially since the Fascinate is starting to get some Froyo alpha builds. It is also probably a bit confusing as to why (since we PRETTY MUCH have the same hardware) it wouldn't work. [Unless you can confidently recover from a soft brick without breaking a sweat on your palms and are willing to risk the small chance of a hard brick] Don't.
.
I would like to clarify a few things. It takes a perfect combination of Kernel, Ramdisk, and ROM etc. to get a properly booting system. Usually, swapping one or two of these for software from another device will cause your phone to stop booting, but won't cause any irreparable damage. Sometimes the device may even boot or seem to function properly. Or -- you might get a lovely brick. Even with a seemingly functional phone, you will most likely have carrier specific settings and other carrier or device (or radio or filesystem) dependent crap in the ROM that will prevent your phone from functioning 100%.
Let me also say this, what works for someone else may not necessarily work for you. What did the last sentence say? When you flash a kernel you don't format the entire device. The device may retain some old configurations or files; the master boot record is left untouched, etc. Flashing a ROM usually wipes your entire system directory. The point is, the way most of these update packages work, you can get different results simply by changing the order in which you flash things or by starting from a different image (what software was previously on your device). I have found this device to be rather finicky. Sometimes, things don't even work for me when I go through the exact same steps or the seemingly "proper" steps. Sometimes things only work after an Odin restore to stock. Regardless, my interactions have caused surprisingly unpredictable results.
I am sending this message because I have seen a few users recently put themselves in frustrating situations after flashing software for the Fascinate. First, I hope you NEVER flash software for another device altogether (Vibrant, Nesux S, i9000, Droid..). With the Fascinate, there is a little more breathing room because there are strong similarities between the devices, but if you don't know what you are doing, I still strongly advise against it. Even the same hardware can have a different partitioning system, master boot record, configuration scripts, etc!
I would like to let you know, WE ARE WORKING ON PORTING OVER the AWESOME FROYO WORK that has been done on the FASCINATE. I am relatively new to the Android scene so it's taking longer than I would like or than I expected (I've also been rather unlucky and encountered some stupid error or silly mistake almost every step of the way). I know you all are getting antsy, but don't worry, be patient, we are working on it. AND, if worse comes to worse and we can't get an alpha build out to you all, I have no doubt we will get at least a beta and a final Homebrew Froyo out there for you all.
Best,
dcow
Listen to the wise man, for those who are patient get to enjoy the spoils of these great developers work, with the least amount of headaches (not to mention the headaches and time saved from dev's not having to help those who make those bad decisions to begin with).
I wish us showcase guys could get our own section
den0ts said:
I wish us showcase guys could get our own section
Click to expand...
Click to collapse
But until then you have to sit in our sandbox and play with us.

[Q] Anyone use tasker to work around wifi bugs?

I was wondering if it would be possible to use tasker to flick wifi off and on when wifi drops and/or 3g activates. Lately it seems on my phone that when I go out of wifi range and the 3g/4g connects the last wifi spot is remembered and almost acts like it is still in range causing issues when trying to connect to the next spot. I already installed the 7 day trial but haven't had as much time to research as I thought. Sound possible? Wasting my time?
rxnelson said:
I was wondering if it would be possible to use tasker to flick wifi off and on when wifi drops and/or 3g activates. Lately it seems on my phone that when I go out of wifi range and the 3g/4g connects the last wifi spot is remembered and almost acts like it is still in range causing issues when trying to connect to the next spot. I already installed the 7 day trial but haven't had as much time to research as I thought. Sound possible? Wasting my time?
Click to expand...
Click to collapse
What ROM are you on? I haven't had any of the problems like you describe since moving to Gingerbread.
Sorry, still stock. I keep thinking about flashing a rom but like others I am hoping for an official release soon with all the updates/leaks. Also this is my first android phone and I don't have total confidence in flashing it. For instance for whatever reason rooting using the "regular" method didn't work and had to use superoneclick. The latest rom thread also seems like a bit of a hodge-podge of things needed to get everything working....no disrespect intended to the individuals working on it.
Sent from my SAMSUNG-SGH-I997 using XDA App
rxnelson said:
Sorry, still stock. I keep thinking about flashing a rom but like others I am hoping for an official release soon with all the updates/leaks. Also this is my first android phone and I don't have total confidence in flashing it. For instance for whatever reason rooting using the "regular" method didn't work and had to use superoneclick. The latest rom thread also seems like a bit of a hodge-podge of things needed to get everything working....no disrespect intended to the individuals working on it.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Superoneclick is the "Regular" method for most people...
Infused 2.x had a few rough patches as he tried to integrate UCKI3/I4 stuff to fix the known issues with the Rogers release, but that has settled down as people have figured out what's broken in I3/I4 and what's not.
Serendipity VII is still stable, Mikey didn't rush to bring in the I3/I4 stuff. If you flash it, you'll have the following issues:
No audio on first call after boot - toggling speaker on/off will fix it (Hellraiser known issue)
No HDMI (won't see this until AT&T releases Gingerbread)
Data speed issues (However the Hellraiser beta9 kernel or my DD kernel may improve this - I am STILL waiting for someone in an area with good speeds to do an A/B comparison between old/new kernels.)
Camera limited to 15 FPS video - but you can flash the UCKI3 camera libs to fix this, there's a separate flashable package with its own thread in the dev section
None of the above bother me significantly (In fact as I live in the boonies and shoot with an SLR, the data speed and camera issues don't bother me at all), so I have been on S7 for a while.
In general you will find that there are VERY few people here running stock Froyo any more.
Good news is that if you screw up, Samsungs are VERY easy to restore to stock. Download mode (aka Odin/Heimdall mode) is awesome.
Entropy512 said:
Superoneclick is the "Regular" method for most people...
Click to expand...
Click to collapse
I guess that is where doubt started setting in about whether I should start flashing the phone or not. Both stickied root threads point to the rage against the cage method and one points to superoneclick being the old method. Thanks for all the info. I wasn't aware off the 30fps fix since I don't frequent the development threads. I honestly haven't had the time to do the necessary research if I get stuck so I have stayed stock.
Back on topic, I did get a chance to look up the some things in tasker and will try it out at work tomorrow since this is where it seems I have the most trouble. I'll post back if it works.

Stable rom/kernel?

I'm running a rooted stock kernel/rom from VM
I wanted to ask in the dev thread but I don't have enough posts for it but I suppose this is more of a newbie question anyways.
If I put in the bkernel http://forum.xda-developers.com/showthread.php?t=1322982 would I be able to use it with the stock rom?
The part about 66mhz support, Whyzor's latest touchscreen driver (don't know what they changed but my touchscreen is driving me crazy), and tethering is always useful. I just want something stable and my phone auto-reboots randomly so I'm ready to try something new.
Not certain but I think you can. Why not give it a try? Just do a nandroid backup before making the change so you can restore your phone if you don't like the result.
If you want improved performance but want to keep the original look and feel of your phone try the 'Triumph Stock Re-Imagined' ROM by chairshot215. I think it comes with a version of whyzors kernal. I am using it and it runs great, Quadrant score about 2700.
On the other hand, to my knowledge there are 2 things CM7 can't do, WiFi and Blue tooth will not operate at the same time and HDMI is broken. If you must have one of those well I guess you need the stock ROM.
That is pretty unfortunate. I don't use the HDMI out very often but it does prove useful when I want to show things off. And I am usually on wifi when I'm home >.<
I was somewhat hoping a stock rom would preserve the HDMI feature (did not see the wifi/bt issue) and I had hoped changing out the kernel would theoretically fix bugs and add features in the background while preserving the other stuff.
I really need to make a nandroid backup, I still use the stock recovery and one click root.
to my knowledge B_randon has 2 different B_kernels available, one for Stock roms and one for CM7 roms, im not 100% sure if the stock one will work on purely stock or if it has to be running a stock froyo type rom, but i cant see why it wouldnt
as for CM7, the having Wifi and BT enabled causes CPU to max and phone to crash is i bug that im pretty sure was resolved in the later builds
the rom by G60madman called CM7 G60 Style Final no longer has this issue to my knowledge, Altho it still does have the issue where leaving Wifi or BT on may cause it to not go into Deep Sleep Mode, but so far all my research has returned is that is a side effect of the workarounds needed to get wifi and bt to function properly
i currently am running the G60 Style Final on my device and i love it, im Not however running it with the b_randon kernel, due to the fact that in my case atleast the cm7 version of the kernel seems to not get battery life as good as the whyzor based kernel included in the rom

light sensor - custom kernels with Froyo stock

I have stock Froyo ROM.
With stock kernel, the light sensor works fine. I can use the built-in auto-brightness (settings/display/brightness / auto), and I can use my own Tasker auto-brightness routine, and I can see the tasker variable %LIGHT change with ambient light level (albeit in discrete steps).
I installed 3 different custom Kernel’s:
Defuse 1.4
Infusion 1.8
Infusion 2.0
With each of these, light sensor doesn’t seem to work. Built-in auto-brightnes doesn’t work. My tasker auto-brightness doesn’t work. Tasker %LIGHT value reads 100 lumens no matter whether you are in a dark closet or bright sunlight.
Just to make sure it wasn’t my phone, I disabled voodoo lagfix and went back to stock kernel again (from a backup I had made). Light sensor works fine once again. It’s definitely something about those kernels.
.
Question 1 - Does anyone else remember seeing this?
(I’m kind of surprised that searching didn’t show this in the general, q&a or developer forums....how could I be the only one to notice????).
Question 2 - By any chance, are any patch or fixes known?
(I doubt it, but just figure I’d ask)
By the way, this is by no means a complaint. I am very happy with the performance of those kernels and plan on keeping them as long as I’m in stock Froyo (which might be quite awhile). I can see the improvement in response time in menus, in swiping home screens (and in Quadrant fwiw). I tested all the other features I can think of and everything else works flawlessly (except possibly some extra flashing from BNL feature on Infusion 2.0, already well discussed in developer’s thread). I am very, VERY grateful to the developers that gave us these kernels last year and continue to work on great new things to share with us.
Probably just some wrong code that needs fixed... and it wont be fixed either, all have moved on bigtime lol. It would also seem useless to go back and change it...
Sent from my SGH-I997 using xda app-developers app
Ryanscool said:
Probably just some wrong code that needs fixed... and it wont be fixed either, all have moved on bigtime lol. It would also seem useless to go back and change it...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
It certainly wouldn't be useless to me. I got 5 Infuse phones for my five immediate family members, and I am sort of the go-to guy within the family for questions. For one thing I might do better helping them if I stick with Froyo (although I haven't quite made up my mind on that... might try for some stable GB either stock or AEON on my phone only) . For another thing, they are not interested in changing things they have figured out, so if I can give them custom kernel with their Froyo, it would make their phones faster wthout forcing them onto a new OS.
But since I don't have any ability to develop a fix myself and as you mentioned, those who do have long since moved on to bigger/better and newer things. So useless or not is probably an irrelevant point... it ain't gonna happen.
It's also weird that the same problem happened on all those different kernels from different developers. Makes me wonder if somehow I'm missing something and doing something wrong on my end, although I don't know what that could be. Oh well.
Thanks for responding.

Lollipop, KK, Ics, JB, TW, AOSP, CM, Recommendations, & Opinions for a dying Device

Lollipop, KK, Ics, JB, TW, AOSP, CM, Recommendations, & Opinions for a dying Device
Well I haven't seen a general lollipop thread so I wanted to start one. The Pub seems like a nice place but since there's so much talk on there about everything in general, info could become hard to find. I do like the pub and read it every so often.
That said. I may or may not update the op with links posted. But most know where to find things if they look hard enough.
What I've found so far are AICP, Liquid, Mastamoon's CM, and a Slimpop build. I've tried AICP and Liquid. Thus far I've not been impressed with Lollipop, to each their own though. It looks okay, seems to run great, (I didn't do any benches, rather relying on the seat of the pants feel), I realize our device is getting at the age where not a lot of further development may happen. But it's still one of the few newer phones that you don't have to jump though hoops to install a rom.
What I'm asking if anything, is what have you tried, and why do you like or dislike it. Again, I know it's early especially for the d2vzw, but builds are out and are fairly stable, on AICP I never had a single reboot that I can recall. I'm going to try the latest Liquid tonight. I don't understand the new DD layers or whatever it is. I think it's a new way of theming possibly used by slim and maybe now liquid since I think they're using slim as a base now according to their thread in original development.
I'm backing up my favorite KK build now. Don't know if I want to try slim first or liquid. Both have builds dated 02-07 and 02-08 respectively.
If you dislike it I assume you're still running KK, or JB. In this case, I'd like to know if you're running a custom TW JB rom such as alliance or Moar or Wicked or anything else. And why. I am in an area where signal is ****. And although I'd imagine TW should get better signal, I'm not seeing a huge difference here. Maybe if I could get 3-5 DB/m better I'd stay on TW JB, but I'd have to make some measurments first. Signal on Lollipop seemed better but it can't be because I'd assume they're using the exact same RIL as on KK. Again, if I'm wrong on any of this please fill me in.
If there is another thread to follow that has already addressed all this let me know. I'm loving lollipop but can't find one namely AICP my current favorite that's releases regularly besides Masta and liquid, that have camera and video working if you have lollipop installed with these things working please share. I've tried freezing camera, then installing OPEN CAMERA, VIVAvideo, CM Camera FIX w/ the added apk for resetting the camera drive without a reboot to no avail. And I can't seem to make VIVA default to 640*480, maybe it does it on it's own but I've looked though all the settings I can find and can't seem to figure it out for the life of me. I've read damn near every thread and q&a thread to no avail.. I didn't read Masta's in it's entirety because it's so dang big. But I did browse the last ten-twenty pages or so. Once you stop keeping up for a few day's you're just lost... Which is what I wanted to make this thread to try to shed light on things without beating anyone up, and without downing any dev's they all make these things possible.
SO PLEASE if you don't mind let me know what rom has worked for you, with camera and video working and what you did to get it going.. WITHOUT STEPPING ON ANYONE"S TOES if at all possible. Thanks and have a great day/night/evening/morning.
Ain't getting a bite. Oh well. I saw a post about the slim ROM like a day later. Haven't ran it but that post has detailed data on what works and what doesn't in the op. I did try the newest liquid from 02-08 I think and it ran fine. I couldn't find how to change which settings though. A lot of features were there some weren't. Tried AICP same deal except I found the quick settings modifier in this one.
Both ran very well but I did use dkp's excellent kernel. Tierservative governor and clocked at 216-1728. Using his voltages.
I did try sending a text with liquid and I don't know if it went or not. I had read receipts checked but didn't get one. Someone else had this same issue in the liquid thread.
I'm back on KitKat but will n be testing new builds as I find them. Please give the developers some love and support or if you can donate. These guys work on this for fun and experience and some are in college. I've never known many wealthy college students. I was thrilled to have a case of naddy light or ughhhh beast ice.
griz.droidx said:
Ain't getting a bite. Oh well. I saw a post about the slim ROM like a day later. Haven't ran it but that post has detailed data on what works and what doesn't in the op. I did try the newest liquid from 02-08 I think and it ran fine. I couldn't find how to change which settings though. A lot of features were there some weren't. Tried AICP same deal except I found the quick settings modifier in this one.
Both ran very well but I did use dkp's excellent kernel. Tierservative governor and clocked at 216-1728. Using his voltages.
I did try sending a text with liquid and I don't know if it went or not. I had read receipts checked but didn't get one. Someone else had this same issue in the liquid thread.
I'm back on KitKat but will n be testing new builds as I find them. Please give the developers some love and support or if you can donate. These guys work on this for fun and experience and some are in college. I've never known many wealthy college students. I was thrilled to have a case of naddy light or ughhhh beast ice.
Click to expand...
Click to collapse
I ran LS and mastas LP roms and loved em both on my S3 (I still have it even though I upgraded) and while I was impressed with the rom itself in both cases the battery life for me at least was horrendous. I've since learned a lot about wake locks and having too many apps can be a bad thing. I'm running slimkat on the S3 currently but I think I might just try out another LP rom seeming how it's only a wifi device now
Sent from my Nexus 5
Thanks. I think my battery may just be getting old but I do have a few wake locks. If your using the s3 as WiFi device then use airplane mode to help battery. Turn it on then turn on WiFi. That should help your battery life a lot. At least on my dx2 it does.
Sent from my SCH-I535 using Tapatalk
This was supposed to be an edit sorry.
Thanks. I think my battery may just be getting old but I do have a few wake locks. If your using the s3 as WiFi device then use airplane mode to help battery. Turn it on then turn on WiFi. That should help your battery life a lot. At least on my dx2 it does.
Out of curiosity what did you upgrade to? I'd love a nexus six but I'm not sure they'll work with CDMA networks or a new moto. Since my old motos DX and x2 are bullet proof. Built like tanks. But I need to get something that'll let me scratch the flashing itch.
griz.droidx said:
This was supposed to be an edit sorry.
Thanks. I think my battery may just be getting old but I do have a few wake locks. If your using the s3 as WiFi device then use airplane mode to help battery. Turn it on then turn on WiFi. That should help your battery life a lot. At least on my dx2 it does.
Out of curiosity what did you upgrade to? I'd love a nexus six but I'm not sure they'll work with CDMA networks or a new moto. Since my old motos DX and x2 are bullet proof. Built like tanks. But I need to get something that'll let me scratch the flashing itch.
Click to expand...
Click to collapse
I upgraded to a Nexus 5, I'm on straight talk so I can get any phone i want. And yea I run the S3 with wifi and airplane mode on, I do the same with my tablet
Sent from my Nexus 5
---------- Post added at 04:40 PM ---------- Previous post was at 04:37 PM ----------
griz.droidx said:
This was supposed to be an edit sorry.
Thanks. I think my battery may just be getting old but I do have a few wake locks. If your using the s3 as WiFi device then use airplane mode to help battery. Turn it on then turn on WiFi. That should help your battery life a lot. At least on my dx2 it does.
Out of curiosity what did you upgrade to? I'd love a nexus six but I'm not sure they'll work with CDMA networks or a new moto. Since my old motos DX and x2 are bullet proof. Built like tanks. But I need to get something that'll let me scratch the flashing itch.
Click to expand...
Click to collapse
The nexus 6 will work with CDMA carriers, it's the first Nexus (other than the Galaxy nexus) to work with CDMA carriers
Sent from my Nexus 5
Dam I want my
I want my nexusss sixxx.
From the old dire straits mark knoplfer I want my mtveeee. When it was an actual music channel.
Showing my age again. Going to test some more and try to keep updating this thread but it's been hectic lately.
Sent from my SCH-I535 using Tapatalk
griz.droidx said:
Dam I want my
I want my nexusss sixxx.
From the old dire straits mark knoplfer I want my mtveeee. When it was an actual music channel.
Showing my age again. Going to test some more and try to keep updating this thread but it's been hectic lately.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Its a solid phone, the price really turned me away from it though
Sent from my Nexus 5
ShapesBlue said:
Its a solid phone, the price really turned me away from it though
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah I really can't afford one, but unlocked devices from major carriers seem to be few and far between. I mean without jumping though every hurtle out there to try to root and rom and device is getting harder and harder these days..
On the lollipop note, I really want to run it and have received advice from various forums on how to get the camera and video to work using A better camera, which i haven't tried, to open camera which i did try, and vivavideo which i just couldn't get to work for me at all. I might try another tonight maybe liquid maybe CM, I'd try Slim which was once my absolute favorite, until I used nameless. It had the features I wanted with none of the bloat I didn't.
I've been trying every aicp that I can get my hands on but have yet to get the camera or video to function.. Of course lots of people are useing Mastamoons CM and he probably has the biggest following of all the rom's out there at the moment. Maybe I should give that a whirl just to see how things fare with using the camera and video. But I can't imagine that other dev's haven't picked up on his tips, tricks, and cherry picks to include in their own roms to make them work just as well, but then again, maybe they're going their own route.
My question to everyone is which rom are you running lollipop that is, that have both camera and video working... Any kind of camera and video. I'm not too worried about resolution at the moment as far as video is concerned as I understand it, VIVAvideo only works at 640-480, but I can't for the life of me find a setting in there to get it to work.
I've found an app on the app store called cm camera fix or similar that is supposed to get things going without a reboot using another apk called camera reboot or simlar, but didn't have much luck with either.. Again, this is using AICP which I love. If anyone can suggest a rom and I've read through all threads except for the massive mastamoon thread, please do so. and please share your experiences
your not so on the spot op
griz
People seem to forget our builds are still alpha builds. Its unfortunate, but the truth. Doesn't seem like we will get any unofficial love until the camera API problem is hacked & working. My favorite devs aren't building for our phone yet because of all the camera issues. Hopefully these issues will be resolved before I get my new phone. Looks like I'll be making the switch back to HTC
sjpritch25 said:
People seem to forget our builds are still alpha builds. Its unfortunate, but the truth. Doesn't seem like we will get any unofficial love until the camera API problem is hacked & working. My favorite devs aren't building for our phone yet because of all the camera issues. Hopefully these issues will be resolved before I get my new phone. Looks like I'll be making the switch back to HTC
Click to expand...
Click to collapse
Sadly there aren't many devs left for the VZW S3 either. A lot of them have moved on. Now that mine is only a wifi device I might just run a LP rom on it. It runs pretty well on my N5, I've yet to have a random reboot which is great
Sent from my Nexus 5
Thanks guys, yeah dev's are getting few and far between and many don't use the device and rely on users for feedback and logcat's and debugging information.
Here's something I posted in AICP and thought I'd post here as well.
Just an FYI. Using suggestions from here and other threads, I've been able to successfully take both photos and video. I used A better Camera as suggested by Pyrite123 so thanks for that suggestion. I first uninstalled the stock camera using ROM Toolbox, I'm sure Titanium would do the same or just removing the apk. Anyway, after doing this and installing A Better Camera (Which is quite nice I must say), and VivaVideo I was able to both take pics and record video. I do not care for VivaVideo, but ABC wouldn't take video... Been thinking about trying LG Camera, this used to work with all else failed back on the DX when dev's were trying to get the camera working on a particular build. LG Camera includes LG camcorder.
On another note, having used DKP, BMS, and KT kernels for sometime now I was afraid those may be inferfering with getting the camera working. Not the case. I've used DKP which should probably be updated to something newer since it's from around the middle of Jan. I like it because of the stock undervolting and many governor options. I usually underclock using the stock voltages to 216-280 and sometimes up to 1728 down to 1350 on the high end. depending on what I feel I need.
Another thing, I noticed my KitKat Rom wasn't locking GPS so I re-installed a stock based rom to get a lock as has been suggested a zillion times over a zillion builds and roms.. Getting a lock in Alliance Rom 23, then immediately installing AICP fixed gps locking.. I got 6 sats locked inside my home tonight with a metal roof, and a huge metal shed outside. I'm certain I could get 10 or more standing still outside.
Just wanted to update and say thanks to not only the AICP dev, but all dev's who are and have been working on lollipop for this device.
Shapesblue mentioned on his GN5, I too have never had a single reboot. Which is one reason I've been so hell been on getting the camera and video working somehow someway.. It may not be working correctly, but it's working.
Looking at masta's thread, it looks like his next build will have the camera fixed. I guess we will wait and see.
Thanks sjpritch25, I saw that. Something about PA having it working but not having anything in Gerrit or something and them possibly just including a third party camera.
My camera works most of the time. I'd say 80-95% of the time.. Yesterday I installed the latest AICP just because it was there, did the camera freeze, and Sometimes Open Camera and A Better Camera would work and sometimes not. usually using the Camera reset apk linked in the CM Camera Fix app in the Play store fixes it in a jiffy so that I can take photos again. I think I even used the front facing camera on one app, don't remember which one. And since another user suggested trying Camera Zoom FX I did that and it worked as well as the others.. All in all the pic's turned out fine with flash, and although one user mentioned that using flash screwed up their Torch Tile in Quick Settings, I experience no such issue.
I had a crazy issue where hangouts would crash and burn horribly upon launch. After installing the latest release, I didn't restore my version from TiBu instead installing it from the play store, and all was right again in the universe.. Again, I'm using the DKP kernel from 01-10 or so what seems like ages ago, but it works and as I've mentioned I like the stock voltages, governors and being able to underclock on the low end, and overclock on the highend if necessary.
Just wanted to report in.
Question, and I should read the BMS thread for this and the G+ community, but Ed has released a couple kernels and I think they're for lollipop, I can't confirm this because nothing in the name of the file says anything about it, but it does say 34, so perhaps KK uses the same version. I just checked and those kernels will probably work, looking in about phone in LP, I see that it's still a 3.4 kernel so I'd say, but I'm just guessing here, that the BMS kernels will work at least the ones release after the date he mentioned including CM12 stuff. Maybe they'll work with both KK and LP. And I'm almost 100% certain this is the case but YMMV. Don't come looking for me if it doesn't.. I'll try one whenever I decide to try another build. I'm itching to try Slim, always loved slim I have, And I reckon RRO Layers are supposed to work theoretically according to the OP. But even though I've read up on that next gen method of theming, I'm still in the dark and need to just dive in I suppose and get my feets wet. I know "feets"
I was on aicp, but flashed mastas build to test the camera. I wonder if PA had video working too? Open camera works great with the latest build. Still no video
I WANT YOUR VOTE!! Opinions Wanted! Not spam... LOL
No I'm not running for public office. I value everyones opinion so please if you have a few minutes read on.
sjpritch25 said:
I was on aicp, but flashed mastas build to test the camera. I wonder if PA had video working too? Open camera works great with the latest build. Still no video
Click to expand...
Click to collapse
Latest Build of what? PA?
As one might have noticed I've changed the thread title. I know a there are a ton of resources about how to do this or that, and listings on what's available for Big Red's S3. Which I will probably own for the forseeable future. I have been unemployed for over a year now, Have had prospects on a few good well paying jobs, but they didn't pan out (One Network Admin Position, I should have landed easily, but didn't have the pull of the board like the other person, but I digress)
The S3 thanks to the hard work of a lot of developers and the community has had a great and exciting life. Hopefully people will continue deving for it well into the future like the DX, or the S2 etc.
My S3 runs great on most any rom I install be it TW, AOSP based, JB, KK, and now pretty dang good one Lollipop. The only problem for me with lollipop is that the moga universal driver doesn't work with L-Pop. This has been noted in the thread, but I don't know if any more work will be done to fix it. So I'll probably go back to TW or KK or JB.
I went from AICP which I have to admit is progressing nicely with their L-pop build. But since the moga universal driver doesn't work I'm going to use something else. And I've got that itch to flash something new again. All the KK's I've ran have been pretty dang good, SlimKat, Carbon, Liquid, Omni, and others but I've always stuck with nameless for whatever reason. Well, one reason is the adjustable timeout to kill apps via back button. Kinda like MIUI used to have.
My question is, for those of you who've flashed a lot of toms and can remember the details because it's all about the details. is what rom did you like the best and why.
Also aside from the massive drawback of not being able to install AOSP roms, is there any benefit to being on the TW 4.4.2 or 4.4.4? I can't remember which one they releaased. Some of the TW roms, Alliance, Moar, and Wicked are great roms and have a nice selection of theme's available. They run pretty good and are running JB.
The JB/KK, mostly KK, roms I've ran run absolutely awesome, I'm currently working on eliminating the play services wakelock without loosing much or any functionality, some say you can use the privacy manager (a big plus for Slim, Nameless, and Other users) to block the app staying awake. I haven't tried to use DS battery saver, Greenify, or many of the other zillion "Install me and I'll magically double or triple battery life using a method called "Using the Force!" At least that's what most ammount to or killing off apps blah blah blah.
Some users I've noticed are Die-hard TW fans and some Die-hard AOSP fans. I strongly lean toward the latter. I like being able to theme my rom I sil love MrDSL's Mixer series and DustinB's Cobalt series. With the new Lpop Roms this isn't possible. I have used the theme manager with CM12 themes in lpop but they're all flat and I don't care for that I do like aesthetics, but to each their own. Maybe the new flat method of lpop makes for better battery life?? It certainly makes for a duller looking rom. I do like the all black ones with white text however. Even they get old compared to the themes for CM7-11.
And TW roms are almost, and I stress almost as themeable as the the older CM varients. So many combinations of this or that and the Ultimate Icon Them or UIT is pretty slick IMHO. The themes for Wicked are almost as Wicked as the ROM itself.
If you made it this far, or just skipped the middle, congradulations you win.... well an opportunity to help myself and others answer a timeless question... Not the chicken or the Egg question.. Not Are we Alone in the Universe, Not is there a God and is he a nice guy, But rather you can help myself and others by giving reasons as to why you prefer one rom over the rest.
Please be detailed or as detailed as possible. Most who are in these forums know the jargon or should, and if not it's past time to learn.
Oh I've posted extensively about the 03-15 ish to 03-25 ish AICP if anyone wants to hear how things are going with that rom. It has quite a lot of the old features many of us miss and now includes the option to adjust the delay in killing apps too a'la Nameless and MIUI (I know the older MIUI did this on my X, DX that is)
So go on kick off your shoes, put your feet up, and write a post about why your running what. I've asked this in the past but opinions change sometimes quicker than it took me to write this short story as one guy used to tell me. Oggie I think it was..
Before I run, I wanted to wish Mastamoon all the best in his future Nexus 6 endeavors. That's probably my favorite phone at the moment, since I used to want a note anyway. SO thanks Masta for all those builds, cherrypicks, news, and releases you whipped up for us over here in Big Red Country, (NO not China, but rather VZW China's more Capitalist today anyway), I've left Verizon for an MVNO called Selectel because of their 15 dollar a month plan using big red's towers, but they don't offer data roaming. Here it's either Big Red or a Regional Carrier (which is probably more expensive than Big Red).
To read my massive off topic thanks to mastamoon press teh magical button.
Since I got way off topic, Here is is: THANKS MASTAMOON for all the work you've done the past few years working for free or next to free I hope someone bought you a beer or beverage of your choice. I can't afford a KitKat right now.. ha ha bad joke.. But thanks man, THANK YOU and thanks again to everyone who's worked on building and maintaining ROMS for this aging device. I for one appreciate it to no end. I used to be a distro hopper, I still am (remember the Mitch Hedberg [RIP] Joke?), I'm still a distro hopper but using Android Distro's for my phones. One an aging DX2, A DX with a screwy, Screen, and my baby the S3. Thanks to the community too, because without their feedback, bugs and stuff may never get solved, and many people wouldn't get the help they need, and just give up with their phone soft-bricked.
So one more for the road Thanks to the Dev's, Thanks to the maintainers, and Thanks to the community. Many don't thank the community enough but I can remember back in my DX says which I was a bit younger but still eager to learn all I could about Android and Customizing the DX. Without the community, I wouldn't have had the guides that get stickied, I wouldn't have got out of my softbrick situatiiiions, my re-activation woes which by the way, with the help of RazorLoves, I was able to re-activate at home which I was told by Big Red that I needed to drive 45min to one hour away to activate because the only towers in my home location and surrounding area belonged to Appalachian Wireless, a more expensive than big red regional companuy, Razor gave me the codes to get into the stock dialer to program the phone. Just one example out of many where the community has been very vey helpful. Kinda like the Dev's are the Doctors in the operating room, the Anesthesiolgist and nurses are maintainers and builders, with the other nurses and guest docs being the community. Probably a terrible analogy. But really. thanks to everyone involved on there. Just wish they got thanked more often and users didn't haggle them about stuff like "when will this be fixed" or "how much longer on the new build" "Rom X dries my dishes while yours only washes and scrubs them", "Rom X is better then Yours" Crap like that gets on my nerves. I'm sure my massive posts and continuous thank yous get on some peoples last nerve, But I'm trying to work on the massive short story length postings. I could care less about what people think of the latter, because the least I can do is thank someone for their hard work.
Back to the rest of the story. Let me know and others for that matter, why you've settled on TW and if yor're on TW, which build and why. If you're on another custom AOSP rom, again, why? What makes it better than any others., and if you're on the new KK locked down one why unless it was an acccident. Because I've even considered takeing that route but I doubt it's that much better than TW4.3 plus there would be no way to go back to lollipop or KK built from CM or AOSP.
I already know most people will say try them out and see for yourself. That's just it. I've tried 95% of the TW stuff, and almost all of the aosp/cm based roms. From Slim which was my DD for a long long time. Slim and I had a serious relationship but we broke it off because after JB she quit doing a few things she used to be able to do very well and I needed them only for my own pleasure. I know not funny, but true.
Just looking for others opinions, whethers its about battery life, signal (I live in a rural area with little signal if any), performance, looks, stability (of the OS not apps), if the Camera/Camcorder works well, so on and so forth.
Thanks for reading something that contained little to no information Also, if you use Xposed, which modules do you use and why?
Thanks in advance, I'll be checking in every day or two until I get my new work schedule.
Your Friend and fellow S3 owner
Griz.
I was wondering what's good for roms anymore I haven't had ran custom since my og s3 since I had it was running ose rom doesn't seem like they are around anymore need to downgrade from nc1 to ml1 thanks
any lp roms yet if any are dd?
nikkifm said:
I was wondering what's good for roms anymore I haven't had ran custom since my og s3 since I had it was running ose rom doesn't seem like they are around anymore need to downgrade from nc1 to ml1 thanks
any lp roms yet if any are dd?
Click to expand...
Click to collapse
I've found a lot of LP roms on the S3 are battery hogs. I'm still running slimkat on my S3 which I only use for games and a mp3 player now
Sent from my N5
ShapesBlue said:
I've found a lot of LP roms on the S3 are battery hogs. I'm still running slimkat on my S3 which I only use for games and a mp3 player now
Sent from my N5
Click to expand...
Click to collapse
would you say slimkat dd? and does it need new ne1 baseband for it kinda wished my old rom dev was still around that I ran was getting day worth of charge on one battery
nikkifm said:
would you say slimkat dd? and does it need new ne1 baseband for it kinda wished my old rom dev was still around that I ran was getting day worth of charge on one battery
Click to expand...
Click to collapse
I'd definitely say slimkat is a dd. I did have to update to the NE1 modem
Sent from my N5

Categories

Resources