yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jakereeves31:
Re: |ROM|| JEDI || Sons Of Android || Build 3 || 3|20

Still digging this ROM. Can't wait for another update:D
[Verizon Samsung Galaxy S III] ruhrohs:
Looks like I spoke too soon. I have noticed twice now that the display gets wonky when I'm reading my RSS feeds through GReader. It's like a part of the screen is zoomed in, while the rest of it is fine. I will close out of the app and come back in again, but the issue is still there. A reboot will always fix the issue.

Yes, I have disabled my profiles I set up in SetCPU and left the governor as Interactive and scheduler as CFQ.

Anybody else noticing this quirk?
[Verizon Samsung Galaxy S III] buffal0b1ll:
Decided I wanted to go back to undervolting so I tried the KT747 03/27/2013 build last night without success. Tried the advice in the KT747 thread about deleting KTweaker from the Superuser log and clearing data for Ktweaker in app settings, but after 3 flashes and constant FC and reboots one minute after boot, I gave up;-( Truth be told, I haven't had good luck with KT747 since the 03/05/2013 build.

It had been a while since I used Lean Kernel so I flashed Lean Kernel 2.9 Experimental with the settings below. Will report back on stability and battery life later;)

EDIT: Removed my screenshots of config because I'm having trouble with settings sticking after reboot.
[Verizon Samsung Galaxy S III] Masa6GCS:
Re: |ROM|| JEDI || Sons Of Android || Build 3 || 3|20

Has anyone else had difficulty getting changes to cpu settings to hold using the stock kernel and setcpu. Every time I reboot the up/down thresholds, freq.

step, etc. that I use for the conservative scheduler return to their default values.

---------- Post added at 11:38 AM ---------- Previous post was at 11:35 AM ----------

I had the 3/14 build for quite a while and it seems to work quite well. Haven't tried any of the newer builds with Linux 3.4 yet though. I'm curious to hear how lean kernel works with this. It was my favorite kernel when I was on android 4.1 roms.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Never tried conservative, but I never had a problem getting interactive/row and clock settings to stick on boot with stock kernel and SetCPU.

I just gave up on Lean Kernel. Both 2.9exp and 2.9 wouldn't hold the 1900mhz max on reboot in SetCPU. Kept reverting to 1512mhz. I could manually change it 1900 after reboot, but who want's to do that? Tried the lkconfig #5 thermald setting too but didn't make it stick either. Tried uninstalling SetCPU and letting stock Performance Control run the show, but then I'd get 2 force closes of PerfContorl after boot, presumably one for the clock settings and one for the voltage settings.

Decided to go back to the 03/05/2013 KT747 and it installed well. Set pegasusq/zen 384-1890, disable touch boost, -50mv across the board. 2 minutes later I black screened but phone was still on cause it rang when I called it. Battery pulled, rebooted and set pegasusq/zen 192-1890, disable touch boost, -25mv across the board. Any more monkey business and I'm going back to stock and interactive/row.
[Verizon Samsung Galaxy S III] ptmr3:
Updated!!!
[Verizon Samsung Galaxy S III] jakereeves31:
Finally!:D
[Verizon Samsung Galaxy S III] Masa6GCS:
One thing I noticed on the new build, not sure if this is intentional. But when the clock is set to appear in the middle of the statusbar the clock that would be on the left hand side of the notification pulldown is gone the only thing that remains is the day and date.
[Verizon Samsung Galaxy S III] droidxxxxx:
Facebook contacts pictures won't sync..and where did developer tab go? No way to keep it on while charging? GPS is kinds wonky..but does work..just not very good..shows you driving in google maps over in the weeds..
[Verizon Samsung Galaxy S III] jackh0lt:
Facebook's a ***** like that. Developer tab is hidden by default in 4.2.2 you have to tap the build number 7 times it will appear. The rest of that stuff will have to be fielded by someone else :P
[Verizon Samsung Galaxy S III] buffal0b1ll:
Build 4 stable after dirty flash. Now on KT 03142013 kernel pegasusq/zen 192-1890, disable touch boost, -25mv across the board.
[Verizon Samsung Galaxy S III] Masa6GCS:
The conservative governor seems to have problems, the cpu speed will slowly creep to max and never drop. I dirty flashed this and I could attempt to get a logcat of this not sure how to go about it exactly for a cpu issue though. The interactive governor works well though so I'm sticking with it for now.
[Verizon Samsung Galaxy S III] jlokos:
I flashed build 4 and LK 2.9 exp. Like the previous build smooth as silk and fast. I will put it through the rounds this weekend. Excellent job Dev's.
[Verizon Samsung Galaxy S III] jcyoun33:
Running great on the update! Sweet job!
[Verizon Samsung Galaxy S III] Dearborn1977:
You're not on a Rev4 phone are you? The voltages are hard set into the cpu and can't be changed. Sucks!
[Verizon Samsung Galaxy S III] Masa6GCS:
You're not on a Rev4 phone are you? The voltages are hard set into the cpu and can't be changed. Sucks![/QUOTE]

No I just installed kt and the ktoonservative and conservative governors are working well right now. I'm not really sure why I am having the issue with the stock kernel.
[Verizon Samsung Galaxy S III] ruhrohs:
To quote Quagmire, Giggity giggity goo!

:p

:D
[Verizon Samsung Galaxy S III] buffal0b1ll:
If you overclock above 1512 and reboot, does the max stick?

Didn't for me in 2.9exp:(
[Verizon Samsung Galaxy S III] jlokos:
It does for me. I'm using both the performance control built-in and setcpu to confirm.
[Verizon Samsung Galaxy S III] ruhrohs:
Where did you find the SOAP Kernel for the SGS3 at?

The only Verizon AOSP compatible kernel that I found was here: http://xdaforums.com/showthread.php?t=2186131

For the Verizon Galaxy Note II.
[Verizon Samsung Galaxy S III] buffal0b1ll:
I'm pretty sure that SOA Build 4 comes with the SOAP Kernel even though in Settings>About Phone it says Kernel Version "3.0.69-cyanogenmod-gb02ec00ptmr#@ptmr3-Inspiron-N5110 #1 Sun Mar 17 23:03)09 MDT 2013"

BTW I had random freeze up yesterday on Build4 with KT747 03142013 kernel. Between the Carbon 1.6@3.4 kernel, the Carbon 1.6.1@3.0 kernel, KT 3.4 and 3.0 kernels, Lean Kernel 2.9 and 2.9 exp, and SOA Build 4 I think I've flashed about 20 times and restored about 10 nandroids this weekend.

Long story short, I'm back on SOA Build 4 with stock kernel. It's still right where I belong;)
[Verizon Samsung Galaxy S III] ruhrohs:
HAHAHAHA!!!! :silly:

I was trying to avoid a nandroid backup and just wanted to reflash just the kernel if necessary.

It seems like the ROM is pretty finicky about the kernel. I gleaned over the other few threads pertaining to the SOAP kernel in the AT&T and Verizon Note II forums. Only thing I want to do is undervolt the kernel. ptmr3 said in one of the threads that he didn't want to enable undervolting, because people would screw up the voltages and think that the kernel was faulty, when it actually was user error.

I snooped around a little and found a couple of things on ptmr3's and SOA's github pages. I think I found the source code for the SOAP kernel, but compiling it is way over my head. https://github.com/ptmr3/GalaxyS3_Vzw-Spr_Kernel
[Verizon Samsung Galaxy S III] buffal0b1ll:
Yeah. Undervolting does help battery, but it can make your phone unstable and it varies from phone to phone and user to user what you can get away with. Also I've found that the undervolting steps you used in one version of a particular ROM, can cause instability in the next release of the same Rom. I use an app called Stability Test 2.7> Scaling Stability Test from the playstore to help figure out if the undervolting will cause fc or random reboot and it helps in this regard.

Until recently, I never had much of a problem following the bleeding edge of lean kernel and KT and undervolting at -50 or -75 across the board. But in the last 2 weeks, I'd had more trouble than its worth messing with these kernels, both 3.0 and 3.4 kernels and roms. I'm sure in a few weeks things will stabilize again and we'll be able to set it and forget it, but for now I'm taking the time to run more frequent nandroid steps along the way whenever I muck with Rom updates and kernels.

At the end of the day I'm happy with SOAP and grateful that I can overclock it to 1900 and manage it in SetCPU. I can still set profiles to improve battery even if I can't undervolt. And I don't have to second guess every little hiccup I encounter and wonder if it's the non stock kernel's fault.

---------- Post added at 10:55 PM ---------- Previous post was at 10:43 PM ----------

Quote:

Originally Posted by buffal0b1ll

If you overclock above 1512 and reboot, does the max stick?

Didn't for me in 2.9exp

Let me elaborate a bit more. My max setting in the slider still read 1900 in perf control and setcpu on reboot, but the running frequency wouldn't go over 1512 until I clicked on 1900 again in SetCPU or PerfControl. Confirmed this by watching after boot the Main Page in SetCPU and examining that freq in current said 1512 and checking time in state and noticing that no time spent higher than 1512.

Moot point because I'm back on stock kernel now, but just wanted to document the behavior I saw.
[Verizon Samsung Galaxy S III] jlokos:
I use CPU spy and can confirm overclocking sticks even after reboot on my phone.
[Verizon Samsung Galaxy S III] ruhrohs:
Is there any way to get the notification sound when you plug in the USB charger to the phone? I kind of miss that from the stock TW rom.
[Verizon Samsung Galaxy S III] annoyingduck:
Thank you for getting the center clock option in here, it was really the only reason I couldn't use this as a dd (I'm so used to it). Restoring apps now. Been looking forward to this rom, as I'm really liking the idea of a clean aosp custom rom without all the extra crap everyone else "has to have".... Ex. Pie!! Who cares about pie, I want clean, customizable, stable android, and I think I've found it!

I'll report my usage, findings over the next few days as the build settles in.

And just to be clear, only 3.0 kernels if I decide to change? Thanks
[Verizon Samsung Galaxy S III] annoyingduck:
Yes, this.... And I cannot get the cLock weather to work. Constantly says no data, tap to update. And nothing happens.
[Verizon Samsung Galaxy S III] buffal0b1ll:
I appreciate how stable this Rom is more and more every day. Never had a freeze, random reboot, or black screen when using stock kernel.

I gave carbon 1.6 and 1.6.1 a try and there were way too many deal breaker issues on both for me. My 2 most wanted cherry picks from carbon (if anyone's listening) are:

-Dark Carbon --makes background black in system toast messages and stock sms among other areas

-disable Developer> Long press back kill current app and add Hardware Keys> Long Press Back Button>Switch to Most Recent App
[Verizon Samsung Galaxy S III] annoyingduck:
Long press back to kill app is the last option in developer options.
[Verizon Samsung Galaxy S III] ptmr3:
I'll look into the dark switch but no promises lol
[Verizon Samsung Galaxy S III] ptmr3:
New build in the next few days
[Verizon Samsung Galaxy S III] mmouse03:
Cool! I just started using this ROM and I like it alot. Looking forward to seeing what you come up with :)
[Verizon Samsung Galaxy S III] zeus33:
The "Dark Carbon" was actually taken from Slim. I don't know if that helps or not.

"Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature."
[Verizon Samsung Galaxy S III] annoyingduck:
Interesting thing I noticed: there is no option to enable a custom app to launch when setting the long press hardware keys feature, but there is the ability to choose "voice search". On other rom's I would actually choose the app voice search. The difference being that when you choose the "show 3 dot menu overflow option", an annoying menu screen appears when you launch voice search using long press (menu in my case), but this does not happen when the option is available to choose any app for long press.

Got that!?!

So I'm basically asking to add more options to the hardware keys area, like choosing a custom app.

I use voice search always, and prefer my apps to show the 3 dot menu (mainly the playstore), but I can't have both on this rom without that annoying menu appearing when enabling voice search.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Right, it's there alright. But I'm requesting that that option be disabled...so that long press back button can be in settings hardware keys where imho it belongs. And Most Frequent App added to checklist for hardware keys. Make sense? Thx
[Verizon Samsung Galaxy S III] ruhrohs:
Speaking of assigning hardware keys, does anybody else experience the issue where the buttons only work as the assigned hardware key, after charging for an extended period of time. For example, I set my long menu to show "more recently used apps" and long press home button to be "voice search". It usually happens to me when I leave the phone charging overnight or plugged in for an extended period of time when I'm at work.

I did a clean install and app restore with Titanium Backup. I didn't do any data restores.

As usual, a reboot clears out the hardware assignment issue.
[Verizon Samsung Galaxy S III] KINGDROID25:
Looking to give this a try been on liquid and I've been getting too many sod
[Verizon Samsung Galaxy S III] buffal0b1ll:
Took about 100 photos at the zoo yesterday -not HDR - and camera/gallery force closed frequently. Not a huge problem because it would work fine I restarted the app so it only allowed me down by a few seconds. Location setting is set to off bTW.
[Verizon Samsung Galaxy S III] m-cat:
So I am having tether issues. I am able to connect other devices to my tether when I use the native, but then I don't have data and I can't figure out a combination of the settings in the WiFi tether app to get it to work. I am going to be in AK for the summer and I really don't want another ROM but I desperately need my tether to work. Any suggestions?
[Verizon Samsung Galaxy S III] buffal0b1ll:
Not sure what causing your issue. I'm posting now from my phone while native tethering WPA2-PSK to my laptop. Works fine while using OPEN Wi-Fi tethering too.

Uninstall any non native tethering apps and reboot. They mess up native tethering.
[Verizon Samsung Galaxy S III] m-cat:
Will try tomorrow.

How's your speed whilst using native tether, compared to a wifi tether like app?
[Verizon Samsung Galaxy S III] buffal0b1ll:
Same. Speed not an issue.
[Verizon Samsung Galaxy S III] annoyingduck:
Think you could add a just percent option to the battery icon choices? I like the way baked did theirs, where the text is bigger than other rom's that have the same option. It really makes life better, and would be dynamite on this rom. I also like the option to add the day of the week to the clock... :)

Been running this for over a week and I am loving it. Battery life is by far the best aosp for our device to date. I have had a few sod's, but nothing like other rom's are experiencing.

Looking forward to what you've got coming down the road. Donations will be happening to, but not till the end of the month as I'm in the constuction trade and people suck this month when it comes to paying their bills! :p
[Verizon Samsung Galaxy S III] buffal0b1ll:
Battery life was 40% better for me on build 3 than build 4. Stock kernel on both builds. Consistently been getting 13 hours with 2.5 hours screen time on 4. Seem to remember 19 hours with 3.5 hours on 3. Just reverted back to 3 to test the theory.
[Verizon Samsung Galaxy S III] jackh0lt:
Um... Yeah. So... Still waiting on the force choke mod to be implemented. That's my only complaint... You cannot believe the amount of people that are still around because I'm missing this mod.

On an unrelated note. This ROM is amazing. Slight flickering of bookmarks in the aosp browser but I haven't had issues otherwise. Also this is the first AOSP/TW Rom I've flashed where I've been consistently been able to get 21Mbps downloads in my town. Pretty impressed.
[Verizon Samsung Galaxy S III] m-cat:
So here is my graph for the day and I haven't had GPS on except for a little while this morning. Has anyone noticed that GPS won't turn off even though everything says its off? Finally had to reboot to get it to turn off. Any thoughts?
[Verizon Samsung Galaxy S III] annoyingduck:
Interesting thing just happened. I updated the theme in running though the playstore, and after the phone rebooted I lost all of my accounts in the settings menu. Google however remained, but all others (Facebook, email, haxsync, etc) had to be reentered. Nova launcher was also lost, as the stock launcher appeared and was in "safe mode", which I've never seen. Had to restore my nova backup to get my homescreen back. Any thoughts...
[Verizon Samsung Galaxy S III] ruhrohs:
Which theme did you update through the Play Store?

I found a bug. I was able to reproduce it a couple of times on my phone.

Settings > Customize > System > Notification Drawer > Enable Power Widget > Widget Buttons > select BT, GPS, LED, Orientation, Sound, Wi-Fi, Wi-Fi AP > then back out and to Widget Button Order > try to sort them and my phone would hot boot. It happened twice. I was only then able to sort the toggles by dragging and dropping them in position #1.
[Verizon Samsung Galaxy S III] annoyingduck:
Bluefire theme, which was updated on 3 other devices with different rom's without issue. Very strange thing to happen
[Verizon Samsung Galaxy S III] m-cat:
What's your find on the battery vs build experiment?
[Verizon Samsung Galaxy S III] buffal0b1ll:
Day 1 seemed like better life, but days 2 and 3 were about the same. I switched back to build 4 with lean kernel 2.9 experimental with some undervolting last night. Hoping this will make a difference.
[Verizon Samsung Galaxy S III] m-cat:
I'm all about about battery life so please keep us updated on your findings. I jumped from build 2 to 4 so I have nothing to compare. I will say though that this ROM is the best 4.2.2 ROM I've been on concerning battery life.
[Verizon Samsung Galaxy S III] ruhrohs:
You are still messing with LK huh?

For me, build 3 was the best battery life. Build 4 is a little wonky on my phone. When I'm using GReader, sometimes the articles will get magnified as I'm reading through it. I don't want to nandroid back to build 3, because build 5 should be coming out soon. I did do a dirty flash from build 2, to build 3, to build 4. I know it's recommended to do a complete wipe, but I was in a crunch to get the rom installed and run out the door.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Lean Kernel 2.9exp seems to have made a huge difference in battery life on Build 4. I'm at 24 hours with 1.25 hour screen time now and I still have 38% battery left.

Settings: interactivex/row, 192-1900kHz, 875-1275mV with roughly 25mV increments up through the range, NO profiles, no gpu overclock
[Verizon Samsung Galaxy S III] buffal0b1ll:
Lean Kernel 2.9exp on SOA Build 4

Crazy Battery Life

Lean Kernel Settings in SetCPU
[Verizon Samsung Galaxy S III] GalaxySII5191:
Is anybody else having WiFi issues. My WiFi will start to work but then it will shut off all by itself and won't turn back on unless I reboot.
[MDA, XDA, 1010 General] jann:
Bit difficult to phrase this - what I mean is, if I put on software that

e.g. deletes a vital Windows file etc., will a hard reset sort it out?

i.e.are all the required files permanently in ROM (including after a ROM

update - such as the o2 UK XDA update I'm about to do).

I'm wanting to experiment with a couple of software titles, and I don't want

to find that the unit is unusable/problematic afterwards (I don't mind if a

hard boot cures it).

Thanks
[MDA, XDA, 1010 General] Fortinbras:
Unless you try to flash your ROM you can not delete or modify any files which are located in the ROM. So if you hard reset your xda will return to its original state.
[MDA, XDA, 1010 General] Guest:
Thanks, was a bit fuzzy on that one
[Galaxy S III Mini Q&A, Help & Troubleshooting] theU20i:
I can't turn on the donwload mode, reboot to system, even flash something.

Any ideas?
[Galaxy S III Mini Q&A, Help & Troubleshooting] Eric_cn:
you have to fix bootloader,maybe you must use JTAG box for it.good luck
[Galaxy S III Mini Q&A, Help & Troubleshooting] theU20i:
Problem solved

OK. I "magically" rebooted to download mode and flashed cwm via odin.

In the morning I was hurrying and didn't write everything here. The recovery was working, the theme was for bigger resolution and I've just seen part of the screen. Before I chose in ROM Manager to reboot to twrp so everytime it booted, it was the twrp. I took out the battery, then put it again, turned the phone on and hold the combination of buttons to get to dwnld mode. I hold it and hold and after 3 reboots I've seen the dwnld mode screen. I was never so happy :)

Thread can be closed
[Galaxy S III Mini Q&A, Help & Troubleshooting] Benzonat0r:
I hope you learned a lesson here today. You cant just flash sh*t to your phone.
[Galaxy S III Mini Q&A, Help & Troubleshooting] theU20i:
The "soft brick" is maybe my new tradition. Earlier I had SE X10MP and I've also softbricked it. That was my 1. Android phone and I didn't know how to fix it. After some time I knew much more about Android and my device. Then I noticed that I could fix it myself. In service they just reflashed the soft. That was everything xd
[Nexus 7 Q&A, Help & Troubleshooting] 1ll3st:
hello all. I really need some help. I let my friend play around with my nexus 7 and he got into the TWRP and accidentally wiped everything off my nexus including the OS so now when i boot it just hangs on the google splash screen. I can get into fastboot mode and the team win bootloader screen but thats it. When i connect to my computer it is not recognized so i cant drag and drop a new boot image. I would just like to have my nexus back to factory unrooted bone stock

Please help me out. I'm new to the android scene and freaked out that i have a bricked device.

Thanks in advance!
[Nexus 7 Q&A, Help & Troubleshooting] kistenschieber:
First of all, stay calm! :good:

If you are able to reach fastboot mode, nothing of value is lost (beside your personal data). You can just follow this guide.

At the end, your Nexus will be as fine as before. And don't forget to threaten your friend not to do such things again if he doesn't understand how to repair it. ;)

P.S.: You don't have to unlock (flashing step 2) and re-lock (flashing step 5) your Nexus as you may have unlocked it before (according to information about installed TWRP). And be sure to use the nakasig/Tilapia image for flashing.
[Nexus 7 Q&A, Help & Troubleshooting] chismay:
is this guy still your friend?! why would anyone go into recovery on someone else's device? sounds like he C.I.A'd you lol
[Nexus 7 Q&A, Help & Troubleshooting] 1ll3st:
Thanks I'll try that guide out tonight after work.

How it happened was I received the OTA update for 4.2.2, but didn't update. So when I let him use the tablet he thought he was being nice by updating for me and when the nexus reset it kicked into TWRP which he thought he f*ucked up and decided to "wipe" what he did. :eek:
[Nexus 7 Q&A, Help & Troubleshooting] olokos:
Odp: [Q] Need help. OS was wiped using TWRP v2.3.2.1

That's the reason why I don't let anyone (even my best friends) to do anything on my phone without me looking what they are doing ATM. You should have done the same.

All your data you've had on your phone/tablet is permanently gone, all you have to do now is to restore your os from a backup (if you have made backup before) or flash other ROM and you are good to go ;)

For the future knowledge - if you can access any recovery mode it's almost impossible that your phone is bricked. If you can only enter fastboot there is like one percent chance of this that your phone / tablet is bricked.
[Nexus 7 Q&A, Help & Troubleshooting] c.m.b:
You could flash a recovery with fastboot < fastboot flash recovery recovery.img > (just necessary if TWRP got wiped during the update) and then push a ROM with adb.

This method wouldn't delete your SD card.