yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] jeffsf:
Hmm, interesting. I don't have "Light Sensor Filter" enabled, but do have "Allow light decrease" set. I also have the "Decrease hysteresis" set to 0%.

I think that it might be the "Decrease hysteresis" setting that may be causing the effect you see. If there is 50% hysteresis on a level of 10240, I am guessing it won't "shift down" until you get to 5120. I haven't checked the code on that.

I'm hardly saying my settings are "optimal" -- I intentionally turned off filtering and hysteresis so that I could get rapid response to see how the various brightness levels "worked" (at least for me) in different lighting conditions.

Edit: Kato, what kind of light levels do you have in, for example, your office or home? Your breakpoints seem very high compared to what I would expect.

I'm running:

(0) - 1

50 - 32

75-45

150 - 64

600 - 128

1750 - 180

5000 - 255
[Samsung Galaxy S (4G Model)] TrenchKato:
I just realized that it its the light decrease setting that is causing the brightness to stay at high level... and it makes sense that a 50% hysteresis world cause flicker given that 50% world move thru 3 brightness.. I also have my dim set to 1...

I am actually outside... I didn't take that into account... however it is my preference to use the lowest values possible inside... so my values may be biased in that way.. especially when outside lux reads well above 10240 anyway (on AOKP)

That why I'm thinking using exponential set of values would work better in both conditions than just cutting values in half
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Ya so thank to Jeffsf that we have Auto Brightness working now...so...not to hhijack this thread but for those who are a zip-jockey like me or who dont want to wait til your rom be updated (miui, remics, cna,...bla bla bla) and wanna do some experiment, here is what to do:

Afterward, use apktool (recommend the latest 1.5.0 version) to decompile YOUR rom's framework-res:

$ apktool if framework-res.apk
$ apktool d framework-res.apk

and looke for the file: /res/values/arrays.xml

Scroll down to this:

<integer-array name="config_autoBrightnessLevels">
<integer-array name="config_autoBrightnessLcdBacklightValues">
<integer-array name="config_autoBrightnessButtonBacklightValues">

And change whatever values of those to this:

<integer-array name="config_autoBrightnessLevels">
<item>50</item>
<item>75</item>
<item>150</item>
<item>600</item>
<item>5000</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>1</item>
<item>32</item>
<item>45</item>
<item>64</item>
<item>128</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessButtonBacklightValues">
<item>255</item>
<item>255</item>
<item>255</item>
<item>0</item>
<item>0</item>
<item>0</item>
</integer-array>

After that, compile back the framework-res.apk

$ apktool b framework-res

And open the ORIGINAL framework-res and the /dist/framework-res by winrar in Windows or zip manager in ubuntu and copy the resource.arsc from /dist/framework-res to the ORIGINAL one and copy the modified original framework-res.apk back to the zip (that now contains boot.img, /lib/modules/* and /lib/libsensorservice.so) under the path: /framework and ya...flash it ^^ (you can use the hefe 0.8.1 for the package template and replace files under needs)
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi Dao

Thanks. I tried that on MIUI.

I see the team acid kernel was updated but I don't think auto brightness is working. I see no change when choosing it on quick toggles.

How can I know that it really works?

10x

sent from me
[Samsung Galaxy S (4G Model)] getochkn:
It works in FB's latest AOKP release, I tried it and saw it work fine, so jeff's changes work. Exactly what needs to be used to bring it to another ROM though, ???
[Samsung Galaxy S (4G Model)] jeffsf:
I don't see any logcat evidence in the version of CM9 I am currently running. Using ddms and watching frameworks/base/services/java/com/android/server/PowerManagerService.java (or its equivalent) would be my suggestion.
[Samsung Galaxy S (4G Model)] itzik2sh:
Thanks. I had some other non related FCs. Now that they're fixed I can see it is working. Ghanks guys!

Updating HebMIUI ROM.

sent from me
[Samsung Galaxy S (4G Model)] getochkn:
I tried to do this on your ROM and I get W: Cant find 9patch chunk in file: "drawable-hdpi/switch_thumb_pressed_holo_dark.9.png". Renaming it to *.png.

Not sure I want to continue if I get errors.
[Sprint HTC EVO 4G LTE] jspsuperman:
Im curious if anybody knows if ISIS ends up beating out Google Wallet, will it work on our phones since we have the NFC chips required? Will we be able to use either or when isis becomes available? I know Sprint is the only carrier supporting GW and all others are gonna support isis. I guess Im just hoping if GW does end up failing that we can use isis instead.
[Sprint HTC EVO 4G LTE] om4:
I would think that you need a device certification or some other nonsense for the carriers to keep a tight leash on it but its just a guess
[Sprint HTC EVO 4G LTE] jspsuperman:
I would hope that sprint will use it also since all other carriers are. I would be sorely dissopointed if GW fails and am stuck with a nfc chip I cant use for its intended purpose :( I actually use my phone to pay for stuff at 7-11 and various other places all the time lol
[Sprint HTC EVO 4G LTE] om4:
Actually the cm team has an open alternative for cm9 right now. Once the development on cm9 is far enough along I'm sure the developers will bring to cmx. You could then just unlock and flash.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Hashcode:
My goal is to merge in support for the 2nd gen Kindle Fire into my existing 3.0.31 kernel which is already running JellyBean on the 1st gen device.

I'll update this thread with more information as I get it.

Requirements: the device needs to be rooted and the signature check bypassed in some way to support loading a new kernel and ROMs. There is another thread in this section to discuss that.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] padest.com:
Hi, hashcode!

i have two questions:

1:do you think there are many hardware differences between 2nd gen and 1st gen kindle fire? as i known, the cpu upto 1.2GHz, the RAM upto 1GB, that's all.

2:can you make rom and kernel which support both 1st gen and 2nd gen kindle fire?

thanks!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Hashcode:
Right now everything i see in the kernel source says the devices are exactly the same with the 2 exceptions you mention.

I do think that Roms can be built to support both devices at once. :)
[7" Kindle Fire HD Q&A, Help & Troubleshooting] 2390:
Then why can't I install the kindle fire 2 rom on the original? I am not very familiar with Roms but I took an existing ics rom for kindle and switched out the systems and it went through TWRP but it stuck at the bootloader. Any ideas? I just really want the launcher. How can I go about doing this?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] naddel81:
locked bootloader on new Fire?

tgdaily.com/mobility-features/66202-next-gen-kindles-have-locked-bootloaders

The kindle fire can be bought here in Germany starting tomorrow. I don't know if I really want one if those devices cannot be made compatible with Jelly Bean.
[Sprint Samsung Galaxy S III] DKJae:
it mounted just fine at first but after flashing a rom and kernel, it won't mount at all.. my laptop mounts it just fine.. any clues? or help?:confused:

my sdcard is sandisk 64gb

/edit

now it's on stock rooted rom with trinity kernel.. still no luck
[Sprint Samsung Galaxy S III] stu5797:
Same happened to me. I had to have the card reformatted to FAT32

Download EaseUS partition master
[Sprint Samsung Galaxy S III] iomega311:
Yup. It's because it's not formatted in fat32. Format and it will work fine.
[Sprint Samsung Galaxy S III] reborns14:
fat32 = 4gb -1 byte file size limit

that means no pr0n files bigger than 4gbs for you! jk :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RacerX1911:
Does anyone else have this problem? Man this stupid update was a big mistake for me all the way.

Vol up + Home + power used to work for me before

Damn you Bell!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] betaboy00:
I believe it will revert to stock recovery and unroot your ROM as well.

You will need to redo everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatsupnow:
Didn't happen to me I'm still golden
[7" Kindle Fire HD General] kinfauns:
I've exchanged several PMs with pokey9000 today. He has taken a look at the software update packages for both the 2nd generation KF and the 7" HD. The MLO (xloader, 1st stage bootloader) is signed and the boot header is the type used for HS (high security) OMAP devices with the M-Shield turned on. If the setup is comparable to the Nook Tablet, this is not good news for those hoping to modify these devices in one way or another. The Nook Tablet's exploit was to utilize the external sdcard as an alternate boot device and that doesn't really help with these 2nd generation KFs.

It's all subject to verification by someone who has a device in hand, but it doesn't look good. This is not to say that it's impossible, but it will be considerably more difficult to manipulate these devices than their 1st generation cousin.

So, let's all hope for the best, but be prepared for the worst. If you plan to buy one of these devices, buy them as an Amazon tablet to be used in the Kindle Fire ecosystem. Don't buy them expecting to run Jelly Bean the day after tomorrow.
[7" Kindle Fire HD General] fattire:
Some clarification... and much left unanswered...

Not quite right. NT's exploit was far more complicated than that and has nothing to do with using the external SD card (or depending on one). It could have been done simply with root (or any other method for overwriting a partition, which was required to insert a 2nd unsigned bootloader into the boot sequence). If you're curious, you can look at the CyanoBoot 2nd bootloader for NT description or source to see what's going on.

I've taken a VERY quick look at the bootloader source for the HD7 as well, pushed here for anyone who wants it. There is in fact signature verification code in the uboot source (~line 140).

Also, looks like there are three configs-- bowser, jem, and tate. I have to look at it closer but it looks like tate is a subtype of bowser, and the HD7 I assume is tate. Hashcode also found a "radley" in the kernel code, but I haven't looked at that.

Anyway.. it is possible that bauwks' flaw or some other flaw exists in this signature verification code, but the code isn't identical to NT so who knows.

Incidentally, the new revision of the Kindle Fire (otter2) also has the same code, and there's a thread about the signature issue here as well.

Yeah.. it all depends on whether there's a flaw as there was with the Nook Tablet... someone get bauwks on the line :)

Meanwhile, I'm enjoying my free (as in speech) Nexus 7... :P
[7" Kindle Fire HD General] pokey9000:
Technically true, but altering the boot chain with a removable microSD makes it a reversible process. Overwriting the boot image on emmc without any other boot options is serious brown trousers time. Now if they left in fastboot, then its not so scary if a similar hack to the NT can be done. Still, with no possibility of USB boot there's no recourse if any exploits get patched.

Yes.
[7" Kindle Fire HD General] kinfauns:
Thanks for the clarification and your input as well. I just wanted to get the discussions going on the possibilities of opening up this device to development, but also temper some expectations. There are many people waiting and some undoubtedly have ordered with the assumption that these 2nd generation devices will be getting the full range of development enjoyed by the original. I was mostly paraphrasing and summarizing, so I'll leave the details to those with the know-how.

I'm sure many people will be scouring the code and tinkering with their new devices in the coming days to figure something out.
[7" Kindle Fire HD General] fattire:
Boring stuff...

It's not THAT risky, I don't think. Even w/o SD card on NT, the safe(st) way to do it would be to replace the recovery partition with a 2ndboot/cyanoboot-enhanced recovery.img from a normal rooted boot. If recovery fails, you're still okay-- you can always just boot normally, gain root, and replace recovery again. If you're verified good, then use recovery to replace boot.img.

On NT, the normal secure boot sequence is unaffected when you replace recovery. That's because on the NT, you are never removing or touching the original uboot (ub1), so there's not much danger of a brick as long as you always have two means for booting (normal + recovery).

This is all academic as far as KFire HD goes, as I'm guessing from existence of the "crypto" partition that bauwks' bugfix won't work. I need to give a look at the signature verification stuff, as I haven't looked at it yet, but I'm not particularly optimistic.

True, although w/NT, BN can only patch it by modifying the hardware, which would create massive support headaches for two versions of the boot. This is because w/unchanged hardware, the current, signed xloader->ub1->ub2 chain can always be used to load whatever. Again, I have more clarification on this-- if you're not already familiar with the details, find me on IRC.

speaking of fastboot, apparently if CONFIG_MACH_BOWSER_SUBTYPE_TATE is set, fastboot_idme is defined and fastboot and other debugging stuff seems to be turned on. I'm pretty sure "idme" is a uboot command. It's commented-out of drivers/fastboot.c as a shortcut to be enabled for TATE only.

FWIW, here are some various versions of the bowser board:

Bowser-Jem-PreEVT2-

Bowser-Jem-PreEVT2-

Bowser-Tate-PreEVT2.1-

Bowser-Tate-PostEVT2.1-

Bowser-Tate-PostEVT3HS2-

Bowser-Tate-DVT-

Bowser-Tate-PVT-

Bowser-Radley-

tate = product id 7

jem = product id 8

radley = product id 9

HS is High Security, I'm pretty sure.

Someone apparently is a fan of To Kill a Mockingbird (Boo

Radley

, Atticuls "

Jem

" Finch, Heck

Tate

, etc.). I don't know what the Bowser connection is... this guy? Or maybe just one of these.

Gotta go.
[7" Kindle Fire HD General] bournezhang:
software RD of AMAZON said it was impossible to crack the NEW KF system, unless u know the key in the machine
[7" Kindle Fire HD General] wrexus:
This was probably done in response to all the bricked Kindle Fires that were returned with the original Fire. That and the fact that if they didn't, it probably would have meant a price increase due to increased warranty expense. However, it seems i would make sense to simply allow an owner to pay a small fee to unlock the boot loader and register a modified Fire as "no warranty" for software issues.
[7" Kindle Fire HD General] psomero:
I got my 7" Fire HD in the mail yesterday and am in this 100% to see custom roms running on it.

While I have just under a year of Android tinkering under my belt and many more years of experience playing with pc's and various flavors of embedded systems, I dunno where it all begins for this new device, but I want to help the dev community in any way I can.

If anybody has specific requests about the device or needs to test out something on one, I don't mind being a guinea pig, as long as there isn't too much risk of bricking my cool new toy...
[7" Kindle Fire HD General] deeper-blue:
I will take a look at the u-boot sources of the new fires too and see how/what they have changed. Very possible that they fixed the funny flaw in the loading process for this iteration of their devices.

It would certainly be sad since a full HD android tab is tempting. At least for the 7inch category we have the nexus7 as an extremely good alternative.
[7" Kindle Fire HD General] thebrave:
Ifixit has a teardown of the device, and there is a big test point labeled "USB BOOT" on the main board, and two smaller ones labeled "RX" and "TX"....

http://guide-images.ifixit.net/igi/UapMeZFPXthjTrEn.huge
[7" Kindle Fire HD General] JaxDomino:
Returned

I have already hit the Return Item button on this. I could care less about the speakers and the screen! Gonna pick up the Nexus 7 instead.
[7" Kindle Fire HD General] bournezhang:
just wait for pokey9000 to answer ， wait for u have idea how to USB boot it
[7" Kindle Fire HD General] robertc88:
Well I for one will be quite happy if someone can get an alternate launcher to work without rooting. Didn't have to on the original KF for them to work.

---------- Post added at 12:50 PM ---------- Previous post was at 12:46 PM ----------

I hope not cause the Nexus 7 for those two things ain't as good as this Fire HD.
[7" Kindle Fire HD General] DrWowe:
Worst case scenario, there's always the kexec option. As a last resort, it works even on devices where the bootloader was never cracked.
[7" Kindle Fire HD General] ZilverZurfarn:
Yes, that would do it for me too (along with some ability to sideload apps). I preordered the 8.9 HD so I'll keep close watch on the development. If no solution is found before end of November, I just might cancel, and look around for what's hot (and rootable) at that point.
[7" Kindle Fire HD General] pokey9000:
USB boot needs a special boot loader (aboot in omap4boot used in Firekit) , and at least on the Nook Tablet it needs to be signed too. I doubt that TI's customers can or would opt for locking just flash boot so I'm going to assume that it won't work on the new Fires without a signed USB loader.
[7" Kindle Fire HD General] smirkis:
glad to see everyone brainstorming over here. sorry for the bad news. i'm gonna follow these closely as i want to get a kfire hd for the gf eventually, but only when this bootloader gets unlocked. til then, back over to my n7 (which i find boring at times, because everything just works... bummer) lol
[7" Kindle Fire HD General] Loglud:
fattire is a beast for doing work on the Nooktablet with me, chm and all the other guys.... From what im reading, its actually kinda like booti from the Nook tablet. Very very interesting file at ./common/cmd_idme.c It seems as though theres a way to load a debugging kernel. Kinda curious if we can use that to smash a new boot into it. The following lines interest me:

./common/cmd_idme.c

#ifdef ENABLE_DIAG_KEY
if (!val_vol_up && val_vol_down) {
/* button up is pressed only */
printf("Tablet: Enter dkernel mode: ....\n");
*ptn = pdkernel;
}

case '2':
printf("Select Diagnostic image\n");
*ptn = pdkernel;
break;

and also this line in the ./include/config/tate.h

#define CONFIG_DIAGNOSTIC_BOOTCOMMAND "mmcinit 1;mmc 1 read 0x580 0x81000000 0x600000; bootm 0x81000000"

As for the boot hole that bauwks discovered on the nook tablet, it is not on this device, though it is highly possible that if this Diagnostic mode can be activated we can use the same exploit as we used with the fatload and the booti. This CONFIG_DIAGNOSTIC_BOOTCOMMAND can maybe do the same thing with something in the SAR memory, so its worth someone doing somemore research.
[7" Kindle Fire HD General] adrian816:
One way to make the device harder to alter is by making these test points the physical connections for a bootloader USB port. Perhaps the USB port accessible to the user is solely intended as a data transfer port for multimedia where the driver is initialised only after the anti-hacking measures are loaded?
[7" Kindle Fire HD General] Entropy512:
This is standard operating practice. You can be assured that if flash boot is locked, USB boot will also be locked.

Interesting tidbit: While no Samsung Android device other than the Verizon GS3 (and rumor has it, upcoming Verizone Note 2) has a locked bootloader in terms of ability to boot a kernel, nearly ALL of them have the initial first stage of boot locked. It's just that Samsung usually drops the chain of trust early on. This is, for example, why Unbrickable Mod doesn't exist for any GS2 or GS3-family device - No one has access to a signed USB-bootable IBL/PBL/SBL setup. (Technically, one could likely USB-boot the existing IBL, but that IBL is hardcoded to go to flash for PBL/SBL.)

So far, no one I am aware of has ever compromised the low-level hardware enforcement of OMAP4 HS or Exynos4. In all cases of OMAP4, any compromise took advantage of holes in the chain of trust farther down the line - however nearly all attack vectors are known, so probably every compromise technique that is standard (kexec, second init, etc.) has a countermeasure in play with the KFHD if they're THAT confident in its unbreakability. In the case of Exynos4, in all current cases the chain of trust goes "insecure" so early that only people with clobbered bootloaders care.
[7" Kindle Fire HD General] lbcoder:
Holy crap, that was a seriously high violence tear down.... :eek:
[7" Kindle Fire HD General] thebeastglasser:
Tell me, would anything used on HTC phone be of any use? i.e. unlimited.io

I know they were a huge pain to crack, and many of them had hardware exploits as well as software exploits. For example, for my Evo 3D (Evo V 4G) you had to connect the GND to the PIN on the back. By doing so, it allows you to obtain S-Off while the Juoponut Program is running in the background. This leads me to believe that if anyone was ambitious enough to take off the back cover to expose such ports, it may just be possible.

Any thoughts on this?
[7" Kindle Fire HD General] Loglud:
Absolutly true about the chain o trust, however it appears that like many other companies there's a "standard" u-boot which has a small injection hole in it using stack smashing as bauwks discovered. The one thing that I have discovered (from learning from you and adam) is that there's always a loop hole. The ironic thing about High Security is that it has it is its own downfall. As many people have pointed out before, companies do not want to give out the keys, programs and cables required for a secure flash (in this case it is TI). However, in the case of the nook tablet, they do not want to redistribute, nor have the authority to. This leads to the age old question, "How do i make it so that the IT people at the companies can fix these devices, or update them, without having to send them back to us?" Thus comes in the boot holes. As you stated everyone is THAT confident about their HS, however, they usually know that there are untested scenarios (hits why there are updates) that can cause things to go catastrophically wrong. Insert boot hole or a location where an IT personal or a distributed update can hook on and rewrite the bootloader (from initial to post). The cost of shipping every device back and having every device re verified and tested by the "secure" computer and components is astronomical, and the cost of shipping every IT support personal a Debugging or Re-Flash kit is a security risk for redistribution (like the SGSIII). Thus we end up with boot holes. I agree with you that alot of them get patched, in this case you'll notice the boot hole that we used last time is partial patched, however it is still there, it just requires a little research to see where and how it gets activated.