yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] LinuxHippy:
Definitely battery. I bought my s3 second hand too and replaced battery with what looked like same Samsung battery on eBay. I had power button problems that only showed up with that replacement battery but took 4 months. I think that replacement was knock off with genuine Samsung paper. Fortunately I kept first battery and power button problem disappeared.

Just went to Samsung.com and bought another battery for $30 after shipping. Cost twice as much but works great!

BTW, that power button problem may be indicative of a bad soldering connection and I was surprised that a battery had anything to do with this. I use on screen icon buttons to turn it off now and just use the actual button when all else fails.

I may have jumped to the wrong conclusion, but the original battery did restore my power button functionality. So, just hold on to that original battery. Charge it halfway and store it... You may need it for trouble shooting someday :)

Marty
[Verizon Samsung Galaxy S III] afaneh92:
Battery is good but maybe you need a clean install and wipe data.

Some app drain the battery.

And poor network connection drain your good and stock battery in less than one hour.
[Verizon Samsung Galaxy S III] loonix:
I had the same problem with stock battery as well as replacement Anker battery. Sometimes when I issue Reboot commands from adb or an app, it just shuts down and vibrates and 50% of the time goes into main boot or recovery if that is where I wanted to go. But my SIII is now 3 years old and even though the power button on the exterior looks ok, I definitely think my problem is internal soldering as sometime even the slightest tap near the power button launches the internal menu to power down/reboot etc. Only annoying thing left in my SIII other pretty happy with this ROM overall. It is SuperLite alright :)

On a side note, since I have an international trip coming up, I was curious about the network settings in the previous page. Mohammad's comments are re-assuring that this will work fine if I have a different SIM card inserted. As a backup I found an old copy of HiAPN somewhere and installed it in

/system/priv-app

Anyone wanting to install this app, refuse the temptation to install it in /system/app even with root privs as after Android 4.4 APN_WRITE_SETTINGS authorizations were changed. Installing it in /system/app has potential to soft brick so be cautious.
[Verizon Samsung Galaxy S III] XxD34THxX:
flashed v4.0 and it has no UI changes... Looks exactly the same as v3.0.
[Verizon Samsung Galaxy S III] cmjester6421:
lets say i take the time to convert this to a .tar seeing as how i no longer can boot but to the gs3 logo and i cant get in to safestrap at all cause the phone no longer can make it to that point do you think i can flash with odin and if so what version

reason for losing the rom was a noob mistake please dont ask unless you need the info i was just in a rush kinda like now

info needed asap this was the rom i was just on
[Verizon Samsung Galaxy S III] XxD34THxX:
Just flash stock NE1 and restart from there.
[Verizon Samsung Galaxy S III] loonix:
Definitely not seeing the Network modes when I tried a different SIM here recently. I am in India for 2 weeks and just got a SIM from Airtel. It is still just two modes to choose from and unfortunately none of them work with Airtel as they are GSM.

Did you have to do something else besides just pop in a new SIM? Like Service Menu etc?

---------- Post added at 02:02 PM ---------- Previous post was at 01:13 PM ----------

A workaround is to install Advanced Signal Status app from Play Store to choose Network Modes (WCDMA Preferred working)

HiAPN for managing APN (working with Airtel 3G. Required to install the app in /system/priv-app)

These 2 are really critical changes one needs to make when using the I535 on different carriers. This should ideally be part of the ROM in my opinion. I might flash it back to stock again as I suspect there are other things missing.
[Verizon Samsung Galaxy S III] cmjester6421:
ive been trying that but the problem im running in to is that i need to flash with odin i get a

aboot fail "everytime"

and

cant find a NE1 DL of 4.4.2 that is stock anywhere on the net this rom was the last one that i had on the phone before my wipe mistake i have my stock backup on the sd card but have a locked bl and could only put safestrap on there that is now not reachable at all if i cant be provide with a stock 4.4.2 NE1 rom DL then thats the reason im asking for a .tar of this rom and if i can get it in theory could i flash said .tar to the phone with odin then do root and safestrap install once its back in working order im just at a softbrick point not hard so this is savable just need a rom that will take to the phone

let me know if you need more info and the only reason im on this topic in the first place is cause this is the rom i just want to go straight back to ty for the help
[Verizon Samsung Galaxy S III] dawgdoc:
See if this link is still active: https://www.androidfilehost.com/?fid=23501681358556816
[Verizon Samsung Galaxy S III] cmjester6421:
it is lets just say that i run in to the same error just in case any clue what could be the problem?
[Verizon Samsung Galaxy S III] dawgdoc:
Odin aboot errors refer to the bootloader not being flashed.

Can you boot into recovery? If so, do you have a custom recovery or the stock recovery installed?

I am wondering what bootloader is detected by the device, 4.0.4 or the bootloader from whatever OTA was in the process of installing. I guess the device may even have a 4.1.1 or 4.1.2 bootloader and broke while trying to take the 4.3 OTA. If you have a custom recovery, some have a built in terminal emulator which will let you read device properties. It may even be possible from adb, but I don't recall how.

If we can determine the installed bootloader and it is not NE1, I would suggest flashing a stock with the same bootloader.
[Verizon Samsung Galaxy S III] cmjester6421:
as i stated in all the above posts i had

stock 4.4.2

tried to flash TWRP (softbricked) then found out that i had a locked bl and moved on after i got the phone to boot again

flashed safestrap

then this rom

tried to do a full wipe but after i did so i then relized that i did not have the rom on the ex_sd i had deleted it my mistake was that i tried to restart the phone come that point i had lost safestrap and could now no longer load the backup that i had on the ex_sd because i now have no stock or custom recovery

i am in fact NE1 i know this cause this was the last rom i had and its NE1 i just want another path to go if this dont work thats also why im asking for a .tar of this from casue come tofind out i cant convert it myself with out tool i dont have was just hoping that would be a new path instead of trying stock and i have yet to do so as i want know know if there could be another problem that im just not seeing at all
[Verizon Samsung Galaxy S III] afaneh92:
Ok let me say another $h!t from verizon we cant flash unsigned system.img but the original stock.

I cant state your problem Im confused.

write down step by step what you done to get safestrap removed.
[Verizon Samsung Galaxy S III] LinuxHippy:
Glad to see I'm not the only one confused here :)

Marty
[Verizon Samsung Galaxy S III] cmjester6421:
...i can only boot to the white samsung boot screen not the swirl "meaning" there is no rom on the phone i did a full wipe thinking i still had a copy of the rom and..... i didnt then for some reason i tried to restart the phone and then when i rebooted poof i could no longer boot to safestrap and the stock recovery is gone because i tried to flash twrp and at that time didnt know that i had a locked bl normally i just grab my dl's when i get a new phone and flash away after root is done but like i said i didnt know the bl was on this phone and could not be removed

come to think of it is the a dl and a way that i could get the stock recovery back on the phone and use the backup of the stock rom i made with safestrap the idea just cam to me as i was typing lol hope maybe that could be done it would be the fastest route at this point
[Verizon Samsung Galaxy S III] LinuxHippy:
The first screen I see is a black screen with Samsung in white and an open lock. This is probably a screen that ss put on my device.

Marty
[Verizon Samsung Galaxy S III] afaneh92:
Download stock ROM from here http://xdaforums.com/showthread.php?t=2795659 then flash with odin.

Root your device then read first page carefully.
[Verizon Samsung Galaxy S III] cmjester6421:
ok im dling this now ill let you know how it goes i think you finally understand what i was looking for

gave you a thanks keep up the good help and work!
[Verizon Samsung Galaxy S III] cmjester6421:
YOU DID IT YOU ARE GOD SIR!!!

flash should be done soon and when it is im going to load your rom back up asap after 2 weeks with no phone and no contact to the outside world words cant thank you in any of the right ways just know till the day this phone dies you have my full support

thanks again bro
[Verizon Samsung Galaxy S III] paperllanterns:
I can't get it to work with 4g. I have decent signal, but when I turn WiFi off it only goes to 3g. The network mode is set to LTE/CDMA, the other option is CDMA. But if I don't click on it it says "Preferred network mode: CDMA/LTE/EVDO" which is leading me to believe that is the order it tries to connect in? I'm not sure.
[Verizon Samsung Galaxy S III] afaneh92:
this a wired issue not solved yet.

flash stock odin then reinstall SUPERLIGHTROM with sim inserted.

Edit: I think I fexed this problem will be included in v5.0

Another gift all languages added.
[Verizon Samsung Galaxy S III] XxD34THxX:
v5.0?

Will this have the FULL s5 stuffs?
[Verizon Samsung Galaxy S III] afaneh92:
most app ported from s5 and note 4 if you need SystemUI like s5 or note 4 notification panel and recent app menu

replace ro.product.name=d2vzw with ro.product.name=SM-N910S in /system/build.prop

I like the orginal UI wont theme the ROM maybe will make an add on and theme soon
[Verizon Samsung Galaxy S III] LinuxHippy:
V4 rom just came out.

Marty
[Verizon Samsung Galaxy S III] XxD34THxX:
I tried the build.prop edit. Didn't work like I wanted it to be. Only the toggles changed a little. My friend loves the ROM, say's its really smooth. Now I have to work on his tmo s4, it doesn't turn on properly.
[Verizon Samsung Galaxy S III] LinuxHippy:
I installed nova launcher and works real well and is very customizable. It's too touchy on the home screen for me. I locked the home screen and it works great now.

Marty
[Verizon Samsung Galaxy S III] cmjester6421:
I was using nova for a bit but overtime noticed some notable glitches that just got in the way try moving to apex I have found that none of the same problems or any for that fact have weathered my brain at all
[Verizon Samsung Galaxy S III] LinuxHippy:
What glitches in nova were noticed?

Marty
[Verizon Samsung Galaxy S III] cmjester6421:
Mostly all crash related like switching tabs in the app drawer crash.... Reloading the launcher from exiting most system apps crash.... Constant redraws when leaving any app and going home or freeze ups then I would have to force stop the app or restart phone I did a lot to fight this with little results over the span of a month or so now I'm just staying with apex
[Verizon Samsung Galaxy S III] afaneh92:
the launcher not fully ported, I will debug this when I have some time.

I will focus on big updates and bugs.

If you update from v3.0 to v4.0 wipe recommended or at least do app wipe data (launcher and clock for example in v4.0 has different package name and will be crashed if not wipe there data)
[Verizon Samsung Galaxy S III] LinuxHippy:
I don't get crashes. Maybe it's because I wiped all caches before I installed slr4?

Marty
[Verizon Samsung Galaxy S III] cmjester6421:
Mohammad

I was and have been doing so from the start I'm just voicing this as I was thinking I was the only one so when I saw hippys post I spoke up
[Verizon Samsung Galaxy S III] afaneh92:
I will solve FC on this apps in next update event without wipe.
[Verizon Samsung Galaxy S III] LinuxHippy:
Maybe this is something u can include in the next ROM build since the app works on the current kernel. This app turns device on and off by proximity and gravity sensors. Effects battery use supposedly by 6% so not everybody would want it. But, if you're buttons don't work too well then this may save your phone:

https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree

Marty
[Verizon Samsung Galaxy S III] afaneh92:
All languages test, flash over v4.0

https://mega.nz/#!M0hAkbaR!YD5BLOmy9EjtoiGt9LcMDio0cKF6mRzooyx2tTmVKvY

V5.0 will be delayed as I dont have time to fix some bugs.
[Verizon Samsung Galaxy S III] afaneh92:
Sorry I wont add an app user can downlod from play store.
[Verizon Samsung Galaxy S III] LinuxHippy:
Just the idea...it could probably be done better (the app) & it's similar to double tap 2 wake but using current kernel.

Marty

---------- Post added at 06:47 PM ---------- Previous post was at 06:17 PM ----------

Actually, using the proximity & gravity sensors is better than double tap 2 wake. I had to disable DT2W whenever I wasn't using a holster because my device would just turn on in my pocket (I could hear it). I have sounds setup with these sensors too but I don't hear the on sound when it is in my pocket...darkness seems to keep it off.

Marty
[Verizon Samsung Galaxy S III] sezamer66:
Is there support for I535PP yet?
[Verizon Samsung Galaxy S III] afaneh92:
In next release, I will send you test zip soon.

also unlock for mobile networks.
[Verizon Samsung Galaxy S III] sezamer66:
OK so I assume you can just PM me the link to the zip when you release it. Also, would I need the KitKat GApps? How'd I be able to know it works fine?
[Verizon Samsung Galaxy S III] cmjester6421:
Feel like I may not be posting in the right place

Look after a few days of messing with this problem I feel like this maybe the best place to ask has anyone seen a problem where when you go to uninstall an app the phone restarts
[Verizon Samsung Galaxy S III] afaneh92:
That strange never happen to me on any ROM or any device

searched google and thats happen to some android users try reinstall ROM and wipe dalvik and cache.

and delete the app that restart the device from /data/app
[Verizon Samsung Galaxy S III] cmjester6421:
I did everything but reinstall the rom and it solved the problem like always you come right out and help ty

My only thing here is that u would like to know if there is a way that I can track down the problem I know now that it not there that can be a bit hard however whatever this was no factors other then installing a game from Google changed on my phone then this started I really think I've had this once before but I just reinstalled the rom problem gone however when things come up like this I like to know why being as I do phone and computer modding and repair and like to have this type of info on hand if I see it again yes I know how to fix what ever it was but I want to know what it "was"
[Verizon Samsung Galaxy S III] afaneh92:
Logcat can solve your problem but you need some knowldge on how to read it.
[Verizon Samsung Galaxy S III] stay-down:
Didn't see anyone else with this problem, my history is my mom had an extra S3 and let me have it. I immediately rooted and was forced to install Safestrap because it was already up to 4.4.2. Anyway first thing I did was install this rom and I can not turn WiFi on at all. It switches over but then after a few seconds goes back off. I am no noob but very new to the s3 as I've never had one until tonight. I didn't insert my sim to connect to 4g but didn't think I had to since I was just going to load the rom and tinker with device. Any help with WiFi issue would be great thanks! BTW I did reinstall rom and still problem the same
[Verizon Samsung Galaxy S III] dawgdoc:
I would suggest verifying that the bootloader and modem are actually what you think they are and that they are the same version. You could do this with Phone Info *Samsung* by vndnguyen from the Playstore or by commands in a terminal emulator. The commands are:

getprop ro.bootloader
getprop | grep baseband.version
[Verizon Samsung Galaxy S III] LinuxHippy:
The terminal commands didn't work for me in super lite ROM 4-no error and blank line given. That app worked and gave this screenshot when all works on WiFi:
[Verizon Samsung Galaxy S III] afaneh92:
Try to flash the NE1 modules its ther in download section.
[Verizon Samsung Galaxy S III] dawgdoc:
Don't know why the bootloader command didn't work. The reason the baseband detection didn't work is due to by error. The command should have been:

getprop | grep version.baseband

I just tried both on my i535 with success. I haven't tried the app on this device. I used it on my i897 and later on my i747.

I forgot about suggesting the kernel modules. They weren't needed with my device, your ROM worked with no hitch.
[Verizon Samsung Galaxy S III] LinuxHippy:
That worked, not sure why the first one didn't yesterday-guess I made a typo:
[Verizon Samsung Galaxy S III] dawgdoc:
These commands are always nice to know. They let people check their firmware without needing to download an app.
[Verizon Samsung Galaxy S III] djteotancolis:
Is there an torrent link for this? I cannot seem to download the ROM, every time i try it fails as my net is terrible
[Verizon Samsung Galaxy S III] afaneh92:
Sorry there is no mirror or torrent but If some one can make mirror for you no problem.
[Verizon Samsung Galaxy S III] sezamer66:
Hey man I'm having problems flashing this on my I535PP. I performed a full wipe through Aroma, chose a bootanimation, installed, and ended up with a Status 7 error. Help, please?

Sent from my SCH-I535PP using a Big Mac and some Ketchup.
[Verizon Samsung Galaxy S III] afaneh92:
Installation stoped on symilinking?

That hapened to me when I had installed SCH-I535PP ROM on my device.

some user reported that installed with no problem try wipe cache and data and system before install and make backup before.
[Verizon Samsung Galaxy S III] sezamer66:
I did wipe everything except MicroSD, I just didn't make a backup. I tried to install on ROM slot. I still get Status 7. I never tried on Stock Slot, and don't want to.
[Verizon Samsung Galaxy S III] afaneh92:
OK let me test more when I go back to home.
[Verizon Samsung Galaxy S III] Yacdogg:
Love It ! ! ! ! updated for 3.0, waiting for 5.0, keep up the great work.
[Verizon Samsung Galaxy S III] masterlo3:
help needed

can i install this rom on the stock partition in safestrap??? i don't have much storage to make a rom slot.... will it be safe to install on the stock rom partition?
[Verizon Samsung Galaxy S III] dawgdoc:
I did so, and I recall reading in the thread where others have also installed to the stock slot.
[Verizon Samsung Galaxy S III] masterlo3:
thanks... flashed it on stock slot and everything is working.... did you update busybox and super su from playstore?
[Verizon Samsung Galaxy S III] dawgdoc:
I believe I picked up the SuperSu update from a download in this forum. I used updates from FDroid on this device, never connected to PlayStore.
[Verizon Samsung Galaxy S III] masterlo3:
oh thanks... this 4.4.2 is a real bummer. wish someone can make android 5.1 or any CM rom work with safestrap :(
[Verizon Samsung Galaxy S III] XxD34THxX:
so...

Will this ROM have any updates now? Or is teh s3 officially dead?
[Verizon Samsung Galaxy S III] afaneh92:
Im busy nowdays but there an update soon just some things to be fixed.
[Verizon Samsung Galaxy S III] LinuxHippy:
Is it possible to get lollipop working on the S3?

Marty
[Verizon Samsung Galaxy S III] XxD34THxX:
Probably not since the s3 never got lollipop and we have the locked bootloader
[Verizon Samsung Galaxy S III] LinuxHippy:
That's what I was thinking too :mad:

Marty
[Verizon Samsung Galaxy S III] arcsum68:
Is there a way to disable the "Connected as an installer" message when plugging into USB?

I really just want to use this as a slave device with my car stereo but it makes me click that everytime.
[Verizon Samsung Galaxy S III] afaneh92:
I will look into it as I get time
[Verizon Samsung Galaxy S III] arcsum68:
Thanks so much, excellent support from you on this ROM. I have always hated that feature of Samsung's stock builds.
[Verizon Samsung Galaxy S III] afaneh92:
Disable Verizon CD Installer all thanks to EMSpilot and Versatile1 for the guide http://xdaforums.com/note-2-verizon/development/guide-how-to-disable-verizon-cd-t2831918
[Verizon Samsung Galaxy S III] arcsum68:
Wow, that was FAST! That seems to work, though the phone crashes when I plug it into a computer, I think the stereo may be different. Before it crashed I didnt see the message like I previously did. I will probably just move the rom to the stock rom slot, I think I read that fixes the crash problem.
[Verizon Samsung Galaxy S III] arcsum68:
I confirmed it does reboot when the radio connects, same as a computer. Will move it to the stock rom slot fix that issue before I go through the hassle?
[Verizon Samsung Galaxy S III] afaneh92:
The reboot issue is due to some selinux stuff in the init binary on the slot roms.

I had talked to hashcode and tell me that but Im unable to solve it I need a tool to edit that binary but he rarely response to me.
[Verizon Samsung Galaxy S III] Carousser:
What was the removed app's name that dealt with auto correct? The app that was "bloatware" removed was the Swype apk, but I don't know which apk is for auto correct.

Also, I cannot send MMS, every time I do it gives a toast saying "Invalid address". I tried googling that, but the answer was to remove the parenthesis around the area code, but that did not work.

Battery life is not so good. Went from 80% to 38% in 3 hours of idle time.

Edit- This rom may not just be for me. The keyboard is very stripped (for my liking), and does not have auto correct, prediction, or really anything (which I can understand from a lite rom). If it's a matter of reinstalling some of the removed apps, could you possibly let me know which ones?
[Verizon Samsung Galaxy S III] h82or8:
Great work with this rom. Nice to have something for those phones that got crippled with the rom update. Just gave my daughter one of these and wanted something a little nicer than the bloated stock VZW. Installed this, popped in a Straight Talk CDMA SIM and fiddled with the APNs to get LTE working with Straight Talk. Thanks for your effort, it's appreciated.
[Verizon Samsung Galaxy S III] LinuxHippy:
I use Google keyboard for SWYPE. Works well :)

Battery performance is better if you put super light ROM in stock ROM slot.

I don't have a sim card in my phone and just use WiFi so can't help with MMS problem. I've never read of that problem on this thread so maybe it also has to do with the stock ROM slot. Make a nandroid backup and restore on slot 1 to see if you can replicate problem. If u do then good chance won't have MMS problem if super light ROM in stock slot.

Marty
[Verizon Samsung Galaxy S III] Carousser:
I just tried placing the superlite ROM on the stock ROM slot.

Still, MMS is not working. I am able to receive them perfectly fine, but when I try to send them, I get "Invalid address entered." I cannot even send them to my own phone
[Verizon Samsung Galaxy S III] LinuxHippy:
I take it MMS is working on the stock ROM? Put your nandroid backup of the stock ROM onto slot 1. If it works in both places on the stock ROM, then u can rule out safestrap.

Marty
[Verizon Samsung Galaxy S III] Carousser:
Yea, MMS was working on the stock rom. I did what you said, and it still worked on the stock rom.

I installed the app Textra, and MMS works fine when sent from that app. It must just be the messaging app; i'm not really sure what's up with it.

I also noticed the battery is still bad; at least what's being reported. I was in a call and when I hung up I Was at 2%, and then the phone died. When I plugged it in and turned it back on after 5 minutes, it then read 50% (although, this is probably just my battery).