yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
http://xdaforums.com/showthread.php?t=1886233

KT747 KTweaker: share and discuss your setting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Thx didn't see that earlier.

AT&T SGS3

TEAM BAKED ROM Blackbean 5

Ktoonsez KT747 Kernel

Medical MJ supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
No problem threads get buried quick around here, very busy place :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bg4710:
SGS3 aokp jb, d2att 3.9.12 by task 650+ktoonsez kt747 kernel

Here are my ktweaker settings, I get plenty of batter on this for what I do in a day but y'all may vary..if you feel you need more I would set it up as follows

Min-96

Max-1350

I/o-sio

Gov-ktoonservative

This was recommended by ktoonsez himself as a good all around performance and battery set up

You also could probably under volt with these settings by about 10

Also make sure that your system performance settings match your ktweaker setting bcuz if not your phone will become hot and unstable! A lot of times will reeboot itself...

Hope this helps if it does please give me a thanks!

I'm new to this site but not new to modding my gs3 and

Im trying to establish myself on this sight
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Got some new settings working great. 10+ hours with extremely heavy use.

96Mhz-2106Mhz

Screen off profile: 486MHz

Scheduler: SIO

Governor: Pegasusq

Kernel: kt747 10/9/12

Rom: AOKP TEAM BAKED

pegasusQ settings:

cpu down rate:20

cpu up rate:10

down differential:10

dvfs debug:0

freq for responsiveness:500000

freq step:9

hotplug 1_1:500000

hotplug 2_0:200000

hotplug 2_1:500000

ignore nice load:0

io is busy:0

max cpu clock:0

min cpu lock:0

sampling down factor:4

sampling rate:10000

sampling rate min:10000

up nr cpus:1

up treshold:90

up treshold at min freq:70

Thx goes to liltitiz for his setup above is $$$

My stable undervolted settings are:

AT&T SGS3

TEAM BAKED ROM Blackbean 5

Ktoonsez KT747 Kernel

Medical MJ supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Try my new settings

View attachment 1397270

View attachment 1397271

View attachment 1397273

No lag when gaming good battery life overall
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I tried some tweaks with bfq and abyssplug. So far I gat better use of the CPU, good battery life, no lag and low latency. Try them and tell me if you get good results.

View attachment 1398339

View attachment 1398340

View attachment 1398341

View attachment 1398343
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I tried some tweaks with bfq and abyssplug. So far I gat better use of the CPU, good battery life, no lag and low latency. Try them and tell me if you get good results.

View attachment 1398345

View attachment 1398346

View attachment 1398347

View attachment 1398348
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Trying this out ATM will see how much battery and performance I can get out of it. I'll post my results tomorrow or later today.

Pegasus settings battery life and screen on time pics:

AT&T SGS3

TEAM BAKED ROM Blackbean 5

Ktoonsez KT747 3.0.45 Kernel

Medical MJ supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Tested abyss a few days not getting as much on screen time as with previous settings

AT&T SGS3

AOKP Task & Ktoonsez ROM

KT747 Kernel OC'ed & UV'ed

Medical MJ Supporter

[SIGPIC][/SIGPIC]
[HTC One S] tylerjholmgren:
My question is what exactly can I do and what cant I do on this hboot? I upgraded thinking nothing of it and yea...
[HTC One S] Behold_this:
You can unlock, flash roms and fastboot flash boot.img/kernels (some roms will now have issues thanks to your new firmware), also you can flash recoveries....that is all. No hboot, no radio (until there are new versions).
[HTC One S] d@rklink:
I think there are just issues in general with this new hboot regarding anything root. I was able to unlock bootloader and install a custom recovery, but it usually takes 2 tried to get into recovery correctly. If I reboot the system through recovery, I will get all the way to the lock ring on my screen and the device just reboots. It happens each time I do anything in recovery.
[HTC One S] Behold_this:
Sorry to say friend, but they may well be something else happening with your device. Many users have been able to use the new hboot for flashing everything except for radios.
[HTC One S] d@rklink:
That's what I was thinking but I had no issues at all prior to the new hboot. When on 1.06 and 1.09 I had no problems with rebooting to and from recovery.
[HTC One S] mbernusg:
I wish we had a 2.35 ruu
[HTC One S] yz250il:
since I have ht e Hboot 1.13 and now 1.14.0002 I cant flash the CM10 rom, just stuck on bootanimation :confused:
[HTC One S] usaff22:
Flash boot.img...

Sent from my locked, tampered ville
[AT&T Samsung Galaxy Note I717] jae2jin:
Hey guys, I made a mistake:

What happen was I was using Paranoid Jellybean on my phone but after the phone kept rebooting on a daily bases I decided to move back to ics.

This is where it went wrong, What happen was I removed everything including factory resets, roms, dav and etc but then my phone rebooted during have the installion without a rom and now I am stuck and I don't want to do anything that can damage more phone anymore. please anyone help.
[AT&T Samsung Galaxy Note I717] Trevino07:
U should be able to DL a ROM on your computer save to SD card then boot into recovery wipe install ROM then should be good to go. Good luck :)

Frijole Powered!!!!!
[AT&T Samsung Galaxy Note I717] Sarius24:
Your not screwed at all as long as your phone shows that you can just recover using a stock Odin flash
[AT&T Samsung Galaxy Note I717] Kyaroru79:
Just boot back into recovery, wipe everything again, and install the ROM you had on your SD again. These things happen sometimes, and sometimes it's a bad ROM file download.

And if worse comes to worse, follow what Trevino07 said; download another copy of the ROM you wanted on your PC and move it to your phone via USB...wipe everything, then load the ROM as usual.
[T-Mobile, Samsung Galaxy SIII] Alanmw86:
hey guys, sorry if these seems rushed...

Going through some legal issues at the moment and I need to know what I can do to get call recording up and going asap?

Does our phone support it? (yes by far to my knowledge)

if so does it need to be on speakerphone or is it incoming outgoing recording?

also is there a specific rom I should look at for the best functionality of call recording?

I had just been debating swapping to CM10 (not sure if it supports it or not)

But I may not be able to do that...

I get no service at my house, I need to use wifi calling or else go outside where i get reception.

Does call recording work over wifi?

Gah so many questions

Thanks Guys & Gals!!!!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I think for call recording apps like skvalexs Call Recorder need to be supported by the kernel. I don't know if stock kernel will support it but if you find his thread here on xda you can download the current release as a trial to see if it works.

There are a few roms which have call recording built in. No real options for it but its there and it works. They'll all be ics based I'm pretty sure. FreeGS3, XquiziT, wanam Lite, I think all have this built in.

I'm not sure how well it'd work on wifi calling, but I don't see any reason it would be any different.
[T-Mobile, Samsung Galaxy SIII] StanSimmons:
If you can get them to call thru a Google Voice phone number, you can call record with Google Voice by hitting the "4" button during the call.
[T-Mobile, Samsung Galaxy SIII] Lord_Kaizer:
call recording is built right into GS3 rom default phone app & maybe someother roms here that i may not know of

------------------------------------

Galaxy S3,The Best Big Thing
[T-Mobile, Samsung Galaxy SIII] fbiryujin:
What ROM is that thumbnail from and does it work?
[T-Mobile, Samsung Galaxy SIII] mt3g:
Pretty sure that was ICS, search more though there is a thread floating around where I found an app that works with our phones on TouchWiz JB I believe.
[T-Mobile, Samsung Galaxy SIII] fbiryujin:
Was it Skvalex's app?
[T-Mobile, Samsung Galaxy SIII] mt3g:
read this thread and the one I linked, I don't use any recorders but I know a lot did so searched around http://xdaforums.com/showthread.php?t=2217881&highlight=call+recording
[T-Mobile, Samsung Galaxy SIII] crusecontrl:
http://xdaforums.com/showthread.php?t=2222741

[APP][1.0] CALL RECORDER!! The NEXT Generation!! [FREE]

Great app I use it and it easy!

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] Cruze808:
+1 incall

+1

Incall can record and store as a mp3 so easy to play on other devices as evidence. Do pre testing as with anything before your actual conversations, Incall only worked on speaker phone for me and I dont know about wifi calling. You might need to use different recording apps for different situations.
[T-Mobile, Samsung Galaxy SIII] stephanes:
CallRecorder (10$) from skvalex + AlsaMixer + aosp + ktkernel work 100% perfect.

If you change rom, you need to fresh install CallRecorder + AlsaMixer every time. If you restore from Titanium Backup it will not work.
[Nexus 7 Q&A, Help & Troubleshooting] tucstwo:
I don't know if I'm the only one or just a among a group of unlucky few but I managed to update to 4.1.2 no problems. Was able to restore root, no problems. It flashed the new bootloader 3.41 but now I can not get into Clockworkmod recovery. I tried installed it through rom manager and I tried flashing it through fastboot commands. I even tried the regular and the touch recovery. Is there a work around to this? Are these recoveries not compatible with the new bootloader? I suppose I can flash the old 3.34 bootloader and try again but does anyone actually know the deal here? Please help me out.

EDIT:

Thanks to SilverPosition and his post here . He has provided us with a link to a working CWM Touch Recovery. I've also been told that TWRP 2.3.1.1 found here also works with the 3.41 bootloader.

Thank you everyone for figuring this out
[Nexus 7 Q&A, Help & Troubleshooting] tucstwo:
Update:

The only solution I found so far was to reflash the 3.34 bootloader in fastboot mode and then reflash my CWM recovery. Then I was able to get into recovery. What I don't understand is that many have been able to get the 3.41 bootloader flashed and then still have no trouble getting into recovery. So what am I missing? I installed the 3.41 bootloader 2 ways just to test. 1, with fastboot commands with the .img and the other in CWM with the .raw file. Both worked just fine updating the bootloader to 3.41 but no matter what recovery is then broken. Anyone got any input?
[Nexus 7 Q&A, Help & Troubleshooting] jpcalhoun:
I have the same issue. I've tried every thing I can think of (except flashing the old bootloader) and nothing seems to work. Can't get into custom recovery (CWM, Goo Manager, TWRP, QuickBoot, ROM Manager), you name it I think I've tried it. I tried to flash CWM 6.0.X.X (can't remember exactly which one) thru the Toolkit but that didn't work either.
[Nexus 7 Q&A, Help & Troubleshooting] rockvoid:
i used "fastboot boot recoveryimage.img" to get into cwm-recovery temporarily...
[Nexus 7 Q&A, Help & Troubleshooting] tucstwo:
CWM will work with 3.34. I can't get it to work no way no how on 3.41.
[Nexus 7 Q&A, Help & Troubleshooting] docfreed:
Cannot get TWRP to work with 3.41 either - works nicely with 3.34.

Is it possible to flash just the important stuff of 4.12 and leave out the bootloader (i.e., keep bootloader 3.34)?
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
Android 4.1.2

Bootloader 3.41

TWRP 2.3.0.0

I got it to work by erasing the stock recovery then flashing TWRP.

fastboot erase recovery

fastboot flash recovery

I also noticed if you do not erase the stock recovery prior to flashing the custom recovery, it creates a "recovery-from-boot.p" file in the system directory. This file causes your custom recovery to be overwritten with the stock recovery during boot up. You will need to rename or delete this file then flash your custom recovery again to make it stick.
[Nexus 7 Q&A, Help & Troubleshooting] tucstwo:
What I did was flashed the entire 4.1.2 and then flashed the 3.34 bootloader and my old CWM recovery back in if you choose to go that route. Its a lot easier to replace what doesnt work rather than pick and choose what you're gonna flash
[Nexus 7 Q&A, Help & Troubleshooting] docfreed:
Thanks - yes, of course you're right. Are you able to repeatedly boot into CWM, make backups, etc... I hate to redo my whole setup again but I also believe that there's an issue with the 3.41 bootloader.

Did you flash the bootloader and CWM with fastboot?
[Nexus 7 Q&A, Help & Troubleshooting] tucstwo:
Use the bootloaders provided in this thread : http://xdaforums.com/showthread.php?t=1929270

There's 2 threads floating around but 1 of them provides to bootloaders in flashable format and the one I gave you in image format for fastboot flashing.

What I did was downloaded the OTA zip from here: http://xdaforums.com/showthread.php?p=32672323

Downloaded Voodoo OTA Rootkeeper from the play store. Backed up my su binary and root access with that app.

Then I ran the ota zip in CWM.

I rebooted. went into Voodoo OTA and restored root access

I used root explorer and deleted /system/recovery-from-boot.p and /system/etc/install-recovery.sh this way it wouldnt keep attempting to flash the stock recovery on boot.

Rebooted into fastboot mode and fastboot flashed the 3.34 bootloader

rebooted the bootloader

then fastboot flashed cwm touch.

then rebotoed and everything works fine.

Only issue is im on the 3.34 bootloader and not the 3.41 one and just want to know WHY?! lol
[Nexus 7 Q&A, Help & Troubleshooting] docfreed:
Thanks - I'll try this tonight and let you know - I'd also like to know why there's so much issue with 3.41 but I'll be happy if I can update.
[Nexus 7 Q&A, Help & Troubleshooting] Broooooook:
I removed the "recovery-from-boot.p" file, and erased the stock recovery, then flashed Clockwork Recovery, but still can't boot into Clockwork recovery. It just displays "boot downloaded image" on the top, then after a few seconds, it boots into android os...
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
I don't know about CWM but I got it to work with TWRP.
[Nexus 7 Q&A, Help & Troubleshooting] tucstwo:
I tried exactly this

adb reboot bootloader
fastboot flash bootloader bootloader-3.41
fastboot reboot-bootloader
fastboot erase recovery
fastboot flash recovery twrp2.2.2.1
fastboot reboot-bootloader

Then into recovery...nothing. Back to the google screen. That's it.
[Nexus 7 Q&A, Help & Troubleshooting] iElvis:
All I did was rename recovery-from-boot.p to recovery-from-book.bak, reinstalled TWRP from GooManager, and everything works just fine.

You have to disable/delete that file in /system or it will restore the stock recovery every time you reboot.
[Nexus 7 Q&A, Help & Troubleshooting] tucstwo:
Nah that's not it. Those files were the first thing I got rid of as soon as I restored root access, before I even bothered to access recovery. If u look a few posts up I told that other member how I installed stuff on my tablet and it included those steps.
[Nexus 7 Q&A, Help & Troubleshooting] iElvis:
Ah--I see that now. I'm not sure which bootloader I'm on, to be honest--I just took the OTA as-is.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
I flashed my device with the JZO54K factory image. Then i flashed cwm 6.0.1.0 via fastboot. I can not boot recovery using any method (recovery via bootloader, adb, terminal, various apps) with the 3.41 bootloader. The only way I have been able to use recovery is to downgrade to the 3.34 bootloader from JRO03D.
[Nexus 7 Q&A, Help & Troubleshooting] wweasel:
I'm in the same ship. Only works using 3.34 bootloader.

Install the factory image or OTA, with 3.41 bootloader stop me from running cwm. Only solution is flash 3.34 bootloader image file to use it again.

Edit: C80 here.
[Nexus 7 Q&A, Help & Troubleshooting] omnikai:
+1, I'm on a C60 revision Nexus 7 and I spent hours trying to figure this out until I flashed back to 3.34 bootloader. Thanks for this!
[Nexus 7 Q&A, Help & Troubleshooting] subvertz:
Back on 3.34 and now I can get root again, but it still won't hold a recovery.

Tried reflashing stock recovery, CWM6.0.1.1, and TWRD 2.2.1. CWM fails with an error, the other two claim success but rebooting to recovery gives me a android red exclamation screen with nothing else. No text or numbers.

The temporary flash of TWRP works and is fully functional using toolkit, but its gone afteron reboot.

I've wiped and strated from stock 3 times now, not much hair left to pull out.

Someone tell me what I am missing....please

(In hopes GreenXSniper is right heres my box info: Nexus7-1B012A, 90OX0MW1100370U, AS NEXUS7 1B/T30L/16/1G/V, FCC ID: MSQM370T)
[Nexus 7 Q&A, Help & Troubleshooting] GreenXSniper:
I have the same problems everyone else is having. Its insanely frustrating. Our first step should be to figure out what all our tablets have in common. I think it may have to do with revisions but that's just me.
[Nexus 7 Q&A, Help & Troubleshooting] gapone:
C80 unable to boot recovery with the new 3.41 bootloader here! Everyone please do the same thing now...

edit: ah there is someone with c60 so I think it's something else then...
[Nexus 7 Q&A, Help & Troubleshooting] mskip:
Did you rename the recovery restore files which will reflash the stock recovery on boot?

Mark.
[Nexus 7 Q&A, Help & Troubleshooting] subvertz:
Sweet! Mr. Skip is here!

Are they supposed to be renamed or not, I will try it again.

After a full wipe and factory reset, I tried the all-in-one which includes the rename step. That didn't give a permanent recovery.

I tried d/ling the images from AOSP and manually put them in the toolkit folders, I d/led new versions from CWM, all combinations, no joy.

I'm still trying stuff with the old 3.34 bootloader. Should I go back to 3.41?

*just saw the update for toolkit! giving that a shot....*

Victory! New toolkit worked like a charm and flashed CWM first try. But how?
[Nexus 7 Q&A, Help & Troubleshooting] mskip:
Magic? Thats what the Toolkits are based on :angel:

I have just pushed an Auto Update for the Toolkit to v3.4 which includes an option to flash bootloader 3.34 for people having this issue.

Mark.
[Nexus 7 Q&A, Help & Troubleshooting] rootbrain:
When I updated manually, cwm gave me a pop up to select the option to not overwrite the recovery. Of course I did and cwm stuck with me. Curious that it did this for me but not others. Using cwm 6.0.1 touch.

Rootbrain
[Nexus 7 Q&A, Help & Troubleshooting] Alex240188:
the problems seem to be stemming from flashing bootloader-grouper-3.41.img in fastboot

its not just recovery that isnt working, i can no longer boot into my rom

but previous version it boots fine.

im just going to try flashing the system image of 2.1.2 and i bet that it will work fine after it
[Nexus 7 Q&A, Help & Troubleshooting] subvertz:
Thats what I got to. First time I have seen it, and it stuck indeed.

Mr. Skip is a hero!
[Nexus 7 Q&A, Help & Troubleshooting] Groid:
I flashed the OTA with CWM and after flashing successfully, I also chose to not overwrite the recovery. Then I got an option to try and keep root, to which I said 'yes'. After booting back up I still have root and can enter CWM recovery from Rom Manager. Mine is a C70. I am seriously confused why some have had the problems stated here.
[Nexus 7 Q&A, Help & Troubleshooting] jpcalhoun:
Well here's what I did THAT DID NOT WORK, LOL:

-Booted into bootloader

-fastboot flash recovery clockwork.img

-fastboot reboot bootloader

-fastboot boot clockwork.img

Bootloader rebooted, paused for 5 seconds and went ahead and boot OS. I wonder if you have to erase the stock recovery and then flash a custom recovery. And, I had already deleted the \system\xxx.p file.
[Nexus 7 Q&A, Help & Troubleshooting] GinoAMelone:
I'm also in the 3.41-don't-work crowd. Tried the recovery-flashable ZIP and the bootloader straight from the google-developers download. Won't boot recovery. Won't reboot reliably. Often sits at the Google logo bootlooping. If I can get it fully powered down, the system will boot.

Back on 3.34 for the foreseeable future.

BTW, C8O.
[Nexus 7 Q&A, Help & Troubleshooting] GreenXSniper:
So I just went complete factory stock 4.1.2 locked. Then I unlocked the device, and tried to root and install a custom recovery, i was able to get root but no matter what I did the device would not boot into recovery. I also tried going stock 4.1.1 and installing the ota via cmw touch, which prompted me to keep recovery from being overwritten(Which has helped some people) and even then my device would not boot into recovery.

This whole thing is really pissing me off because I know 100% I am doing nothing wrong. Anywhere I ask for help people basically say i'm a noob who has no clue what he's doing. I really hope this all was an issue on googles end and they will push an updated bootloader that works with everyone, but for now it seems like i'm going to give up. In the past 2 years I've owned and used over 10 android devices and I've rooted and rom'ed all of them. This is the first time i'm literally stumped. :(

Sorry for the rant, i'm just really fustrated.
[Nexus 7 Q&A, Help & Troubleshooting] jpcalhoun:
What are the draw backs of going back to 3.34. Does it make a difference, other that you can get into a recovery.
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
Not that it helps others, but it was exactly the same for me. Yes to stop the recovery from being overwritten and yes to keeping root. I didn't have to do anything else.
[Nexus 7 Q&A, Help & Troubleshooting] GreenXSniper:
I did the same exact thing and no recovery will boot.
[Nexus 7 Q&A, Help & Troubleshooting] :
I'm having this exact same problem. Would someone be able to post a link to the 3.34 BL so I can revert? Or should it still be in my files somewhere?

[Sent from my Nexus 7. Pardon errors.]
[Nexus 7 Q&A, Help & Troubleshooting] PROlific666:
From what I've heard for those whom it works for apparently you can access recovery directly from the 3.41 boot loader. Other than that I haven't heard anything else. My N7 can't access recovery from 3.41 bootloader either. I really hope they fix this.
[Nexus 7 Q&A, Help & Troubleshooting] GreenXSniper:
Well I just found out that my revision is C6O so it isnt revisions...
[Nexus 7 Q&A, Help & Troubleshooting] Roland Deschain:
Going back to the 3.34 bootloader allowed me to get root, but I still cannot install CWM, it installs thinking it's successful but I still get the stock recovery with the red-gutted Android. :) 3.41 didn't even allow root though, and I had the problems mentioned in this thread with it. Thanks for updating the toolkit to allow for flashing the older bootloader. I had wiped device and installed the 4.1.2 Android update, and couldn't get anywhere trying to get root/recovery back on. At least now I have root again.

I just tried installing CWM through ROM Manager, and it worked, though. Interesting.
[Nexus 7 Q&A, Help & Troubleshooting] MightyBK:
I side loaded 4.1.2 thru adb shell, then installed twrp using wugfresh's toolkit.....no issues on my end
[Nexus 7 Q&A, Help & Troubleshooting] don_ernesto:
newbie question alert

how do i flash the old bootloader

prior to the upgrade, i did a NAND backup using the nexus 7 toolkit, and i have the file boot.img, is this the bootloader?

what commands should i run to restore only it?

thanks
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Get the boot loader from the jro03d factory image. Put the tablet in fastboot mode and run

fastboot flash bootloader <bootloader file>
[Nexus 7 Q&A, Help & Troubleshooting] AusMatt:
It's not just rooted and modded N7s that cannot boot into Recovery.

My N7 is totally stock and I couldn't boot Recovery on 4.1.1 (it just hung) and I still can't boot Recovery on 4.1.2 (Android with red exclamation mark).

I didn't try with Android 4.1 as it updated to 4.1.1 within seconds of me getting the device.