yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] icords81:
Thanks both of you. I have purchased Nova Prime already. I'm currently running CM10.2. I think I'll try out PAC for s and g's. What do I have to lose?!
[Nexus 7 (2013) Q&A] icords81:
Banana...you have been super kind to me. Thanks for your help. By chance could you tell me...do all ROMs customize my kernel?
[Nexus 7 (2013) Q&A] dinesh690:
We, on XDA, don't really approve of 'Best ROM' threads because only you can find which ROM is best suited for you. Also, a lot of the fun of XDA is from testing and trying out new ROMS and seeing which you like the most.

There are many ROMS to choose from on XDA and I'm sure youll find one which suits you.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] shamelin73:
Anyone have strange issues with airview and cases?

I normally wouldn't use a screen protector but one came with the Otterbox commuter so I used it.

My airview seems to jump around with the case and screen protector.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] FourPointedFreak:
I have no problems with mine, using the same setup as you.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] shamelin73:
errr if I take the case off airview works fine......very strange issue
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] FourPointedFreak:
Perhaps part of the case is sticking down to the screen protector covering the screen somewhere. Sounds to me like there is a section of the screen being held down and when you attempt to use the feature, it jolts and jumps around not knowing where you want it to move.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Febby:
I noticed this issue with a couple of cases on my friends. I think it is the cover near the sensors. What they did was remove the screen protector near sensors area and widen up the sensor area if your case covers it.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] shamelin73:
Ya I may take the screen protector off. Don't really need it just need the protection from dropping it
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] shamelin73:
I think it may have been the screen protector as I have removed it and works great now.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I'm comfortable with the process of going from stock to aftermarket firmware: root - CWM - backup - flash away

With three or four STOCK options available for the I777 (Gingerbread, Ice Cream Sandwich, Jellybean), Does it help to start from one stock firmware vs another? is there any advantage to flashing over the latest bootloaders, radios, ETC?

-Cyril

Edit: there are definitely differences in the Sbl.bin files, but there's no indication of what they affect.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
The only thing to take into consideration is that whatever custom kernel you flash to get CWM recovery should match the system version. Otherwise, which version you start with is irrelevant.

You should stay with the original secondary bootloader. As far as I know, none of the official distributions changed the bootloaders. Some of the leaks did have a different secondary bootloader that disabled the ability to reset the flash counter with a jig.

There is a thread in the development forum with all the modems from all the official and leak versions. In general, you have to experiment to find the best one for you, and that will mostly depend on your geographic location.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
In all of the excitement about aocp6 (JB 4.3), I noticed that the first page now states: " ***Make sure you are on jellybean bootloaders before flashing this rom*** "

AOCP 4.6 (JB 4.1.2): " ***Make sure you are on gingerbread bootloaders before flashing this rom*** "

maybe the AOCP team throws that in the post to cover their bases, and doesn't matter for the I777?

With reference to compatibility with the newer firmwares available for the I777, I wonder whether the i777ucmd8 bootloaders would make any difference, IF they are actually different than the gingerbread or ICS bootloaders.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I've never seen any discussion about the changing bootloaders on this phone. But then I don't read much in the AOSP threads.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
...so I asked the same question in the 4.3 AoCP6 thread, since they made mention of the bootloader versions...

fair enough.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
^^^

Read the quote above...

It just shows that what someone says can sound really knowledgable, but in fact...

The original secondary bootloader extracted from UCKH7 full stock distribution: 1,310,720 bytes

and boot.bin: 131,072

The newest secondary bootloader extracted from UCMD8 full stock distribution: 1,310,720 bytes

and boot.bin: 131,072
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I did notice that actually, but that wasn't an indication to me whether there were or were not any differences in the coding. When flashing ECU firmware to vehicles, for every different tune there was different coding, but the file size was always exactly the same. In fact, a file size other than 512kb or 1024kb for AM29f400/f800 eeprom, was our first indication of a corrupt or incomplete file.

perhaps that isn't the case here?
[AT&T Samsung Galaxy S II SGH-I777] dsmboost:
I would imagine that a file containing vehicle tuning configuration data would only have small, incremental changes in values rather than any actual additional lines of code. I think the case is different with a bootloader.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
You're right, the ecu firmware changes were indeed changes in data, vs. additional lines; perhaps the bootloader scenario is much different.

Either way, we're still dealing with a lot of i think, perhaps, and probably. [MENTION=2916435]creepyncrawly[/MENTION] is right, such answers aren't the most helpful here.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
When building, for instance, a windows application, when you recompile the file, the size will always change. Even a small change, such as changing a few text words, and nothing else, will cause a change of at least a few bytes. I'm not sure what tool is used to compile the boot loaders, but I can assure you that if they made any modifications to the files, they would have different sizes.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I put them into winmerge to compare the binaries:

The sbl.bin and boot.bin packaged with the ucmd8 4.1.2 firmware are both notably different than sbl.bin and boot.bin packaged with the uckh7 2.3.6 firmware, despite the fact that the files are exactly the same size for each release.

Withut knowing what those specific differences are or mean, there's still no telling whether there's any advantage to starting with stock gb, ics, or jb binaries.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I'm curious and interested to find out more. However, I don't have any extra time to play with things this week. When I do get some free time, I'll be on it for sure.

We all make assumptions, sometimes based on past experience, and sometimes not. The phenomenon is particularly noticeable in these forums, lol.
[AT&T Samsung Galaxy S II SGH-I777] crt60:
Well for one, I never took the bootloaders and compared them by hex, or compared them at all, and second I'm am speaking in general, not necessarily specific of this rom, regardless if you want to compare the bootloaders and find there is no difference, cool.

But it still stands, knowledgeable sounding or not, it is always a good idea to use the latest bootloaders for your device.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Sounds reasonable. By the way, I hope you didn't take that personally. I'm as likely to say something like that about myself as about what someone else says. cyril279 suggests that the boot loaders from different distributions have different contents even though they have exactly the same file size. It would be interesting to follow up on that.
[AT&T Samsung Galaxy S II SGH-I777] 4-2ndtwin:
Concerning the .bin files in the KH7 and MD8 firmwares... I did a quick comparison of the boot, sbl, and modem .bin files with a MD5 hash generator. Thought that would be an easy way to see a verifiable result as to whether these files are different or not, even though they share the same file size with their counterpart. I included the modem.bin files as well because they share the same size also.

Interesting results...

KH7 MD5 #s

boot.bin = C41E06D0BC3F771ACEC30E85A24F8CDE

sbl.bin = CDDC18420052052890A3600C550FE874

modem.bin = 14BFC172DEC1A919D0CA3DA72A89D079

MD8 MD5 #s

boot.bin = 2F9260234A7442CD368A7BC755E18914

sbl.bin = E35A9BB350CAEF3460012712ECAFCB13

modem.bin = 92037CE8BC5FEB79E8644FC7FEBAAF96
[AT&T Samsung Galaxy S II SGH-I777] crt60:
Though different I would assume allot of the changes with the bootloader are just compilation/release dates. In hex, they are similar enough to figure their code is the same. I guess its main function is to initialize the device and start the kernel, so whatever changes with that, who knows.

They are different in hex and different in md5, even though their size is the same, unless Samsung can target a compilation size, they've been changed somehow.
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
[Q]starting from stock GB or ICS or JB? Bootloaders ARE different.

I didn't think to compare the md5 (like a checksum, correct?)

So we agree that there are differences in between uckh7 and ucmd8.

I didn't see sbl.bin in ucll6, suggesting that the firmware was fine to run on the uckh7 sbl.bin.

The fact that sbl.bin was re-introduced to the ucmd8 release, but was NOT included in the ucll6 release suggests more changes than release date or info, which lends to the AoCP team's advice to use JB bootloaders (for their 4.3 rom).

Although it's only partially relevant, I still wish we had stronger sense of the changes and how they may or may not affect the various firmware installs. I admit that figuring it further is well beyond my level, and I don't have sufficient interest to do the work to figure it out. My ECU forum would have told me to stop conjecturing, reverse engineer the code, and report back with conclusive results.

[MENTION=2916435]creepyncrawly[/MENTION]

[MENTION=813691]crt60[/MENTION]

[MENTION=3338871]4-2ndtwin[/MENTION]

thanks for the time and the input.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Took a few minutes to play around with those files. Used the command line program vbindiff. It compares the hex, and highlights any bit that is different in the two files. Both the sbl.bin's and boot.bin's have more differences than similarities, at least as far as the hex contents go.

Also, in another thread, someone claims that with UCMD8 stock installed, a USB jig will not reset the flash counter. I think that behavior is controlled in the sbl.bin, so if true, that would indicate modification as well.
[Windows Mobile Development and Hacking General] nutitija:
I am trying to connect my XDAii to a remote unit that just spits out its NMEA. I would like to use TAPI to do so ... Once my connection is established, do you think that it is possible to receive the full NMEA stream ?

I have doubts on how to use the readfile API in order to retrieve this information. Could someone give me his opinion ? or some explanation on how this information is retrieved. As far as a i know you've got the TAPI handle that will return the stream ?

i'm confused !!!
[Sony Xperia P, U, Sola, Go] blackassassin3333:
Xperia u is bright enough for indoors but outdoors when Sun is up it's hard to see anything. So my question is, is it possible to increase max brightness of screen?

Also another thing I noticed when I was playing music on speakers volume for same song was higher when played by canvas music .why?

My Xperia u is not loud even when playing with speakers it's volume is less than other androids .

So I want to increase max volume, is it possible?
[Nexus 7 (2013) Q&A] mikeypdizzle:
Tried searching here and in the actual rom nightly thread with no luck. I am running the newest nightly and whenever I pull the notification bar down ,the brightness goes all the way off. It only happens if it is a fast pull down or if I drag all the way to the bottom of the screen. Likewise if I do the same with the quick toggle pull down, it brightens the screen back up.

Like I said I am on the newest nightly, using nova launcher and ElementalX 1.4

Nexus 7 WiFi 2013 32gb

Thanks for any help!

*update* I also notice the same thing on my Galaxy s4, same rom and nightly for tmobile.
[Nexus 7 (2013) Q&A] railed:
You might want to post this in the PAC-MAN ROM thread instead of here. You'll probably get better/more answers or help.
[Nexus 7 (2013) Q&A] mikeypdizzle:
Since I don't post a lot, XDA wont let me post in the development thread :(
[Nexus 7 (2013) Q&A] railed:
Ah, didn't see your post count. Well hopefully someone can come along and help you here. :good:
[Samsung Galaxy W I8150] amr.reflection:
I am seriously tired of battery drain so I am now searching for a governor that would balance between Battery Life and Performance. I read this http://xdaforums.com/showthread.php?t=1369817 but actually I was lost in that large number of governors, so Can anyone simply tell me what governor is the best ? I mainly leave WiFi On but Screen On is not usually for a large time ...
[Samsung Galaxy W I8150] dec0der:
afaik and base on their details. personally, i use interactive+row on stock then smartassv2/ lulzactive+sio on custom.

SmartassV2:

The motto of this governor is a balance between performance and battery

SavagedZen:

Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.

edit:
[Samsung Galaxy W I8150] hundred_miles_high:
I use SmartAss V2 and SIO as governor and scheduler.

Like you, my wifi is permanently on, but screen is not on for long periods, and using this combo since Alpha releases of CM10 onward I have had good results, getting up to 2 days plus on CM10 EOL, and currently on LiquidSmooth 2.9 am getting well over a day from a charge.

Performance is good and LiquidSmooth ROM runs beautifully at stock CPU speeds (I currently use educk's Phenom Kernel ported by Madridii with 370Mb RAM, but have had great results with any Madridii kernel)
[Droid Incredible Q&A, Help & Troubleshooting] wanted167:
hey xda

my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?
[Droid Incredible Q&A, Help & Troubleshooting] tekweezle:
try a factory reset.

hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices
[Droid Incredible Q&A, Help & Troubleshooting] SuzyQangel:
Same problem

My incredible started doing this yesterday, Ive tried this option it doesn't work for me. I can get the menu but it when I choose factory reset or any of the other options it flashes the htc incredible screen and starts the loop again, any more suggestions would be appreciated.
[Droid Incredible Q&A, Help & Troubleshooting] tekweezle:
Is your phone unlocked and rooted/s-off?

It will say so on that menu screen.
[Droid Incredible Q&A, Help & Troubleshooting] SuzyQangel:
Htc loop

No I was getting ready to root it the day this started. Will rooting help this problem?
[Droid Incredible Q&A, Help & Troubleshooting] tekweezle:
having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.

whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.

i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.

if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.
[Droid Incredible Q&A, Help & Troubleshooting] SuzyQangel:
Htc loop

I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol
[Droid Incredible Q&A, Help & Troubleshooting] musical_chairs:
This sounds quite a bit like an Inc I have lying on my shelf. It was a friend's and he gave it to me to see if I could fix it. As far as I can tell, the phone's emmc storage simply failed. These phones are aging and that happens sometimes. Anyway, I tried all the usual stuff, including running RUU's (flashing signed PB31IMG.zip's since the thing had never been rooted and was still s-on), and yeah, just boot looped.

I did get the phone working, but it was complicated and messy. Here's more or less what I did: I was able to successfully run the RUU that updates HBOOT to 1.02 (or 1.07, either one works), which allowed me to unlock the bootloader via HTCdev. (see one of the root / s-off guides if this doesn't make sense.) This made it possible to flash ClockworkMod recovery using fastboot, and boot into recovery. From there, I was able to get to a root shell through adb (plugged into my computer) and proceeded to downgrade and get s-off, following the guide. It now works, though it's running Froyo and there is hardly any space for apps due to the messed up storage. I've been wanting to try this hack on it but I haven't gotten around to it yet.
[Droid Incredible Q&A, Help & Troubleshooting] spappy:
stuck in boot loop, keys dead

I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?:confused:
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Sounds hosed to me. You could try to flash an RUU zip but that'd require use of the keys in HBOOT. If there is an RUU option that does not involve touching the phone, it's possible. Otherwise, no. I guess you could open the phone and check the button connections are there but it may be locking up at the HBOOT screen. Give it a chance to charge up a bit. However, I believe this phone is a lost cause. I seem to be seeing more frequent bootloop phone reports lately.
[Galaxy S III Q&A, Help & Troubleshooting] Abdnormality:
I've a I9300XXELLA Galaxy S III, it's home is UK, but I live in Egypt, I could receive calls, make calls and connect to internet through Wi-Fi and mobile network since then, I flashed a Supernexus ROM on my S III, still the making/receiving calls and connecting to internet through Wi-Fi work, but I can't connect to Mobile Data, the "H" in the upper bar doesn't exist though the mobile data symbol is already green (turned on) APN setting is correct, so I flashed firmware 4.1.2 official ROM, still the same. I don't really know how to deal with it, any help please?
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Basics read first.

http://xdaforums.com/showthread.php?t=2344125

Critical you read the first two posts .

You already have an identical thread please report your post to a mod .

Basics read first.

http://xdaforums.com/showthread.php?t=2344125

Critical you read the first two posts .

jje
[Galaxy S III Q&A, Help & Troubleshooting] sriram231092:
try flashing the base band version of your region.
[Galaxy S III Q&A, Help & Troubleshooting] efrant:
Please do not create more than one thread for the same topic. Continue the discussion in this thread.
[Galaxy Y GT-S5360 Accessories] Angelo Francis Sanchez:
Ultimate for SGY wait for i will post it soon
[Galaxy Y GT-S5360 Accessories] vlc07:
what u r saying use english.....
[Galaxy Y GT-S5360 Accessories] mjz2cool:
it is english?
[Galaxy Y GT-S5360 Accessories] vlc07:
look at topic name...o_O
[Galaxy Y GT-S5360 Accessories] mjz2cool:
maybe it's something that's called like that :p
[Galaxy Y GT-S5360 Accessories] ~Unify~:
Whats this Bleach+naruto ??
[Galaxy Y GT-S5360 Accessories] Ze3rL:
bleach and naruto are 2 popular anime....it must be something based on it
[Galaxy Y GT-S5360 Accessories] DC07:
I request any mod to close this thread......since its not related with accessories and also [MENTION=225651]op[/MENTION] doesn't mean anything with thread
[Nexus 4 Q&A, Help & Troubleshooting] kostasrogue:
Hello! I have downloaded the new version of guickoffice today. After I tried to open a document i noticed that the old intergrated in android quickoffice is still there.... Is that normal?

Thanks!
[Nexus 4 Q&A, Help & Troubleshooting] quendil:
Yes it doesnt update the pre-installed one.

I have safely disabled the old one so i guess you can do it as well!

:)
[LG Optimus L9 P760, P765, P768, P769] amnik:
I am not a professional android developer.

The kernel panic problem on my devices is solved with broad ver. 1.1.:D

I would like to share it to all of you.

Before this I need to have someone to test on it.

Requirement:

LG Optimus L9 P765(tested)/P760

busybox installed in /system/xbin/

Unlocked Bootloader

JB Stock ROM (V20B/V20C/V20D)

Please report these items after testing:

-board versions (cat /sys/board_properties/board/board_rev)

-device versions

-Problems

If you would like to have a try, please leave me a PM and I will send you a link.

Also welcome devices with other broad version.

P.s. Voltage control is added. Please use setcpu to change it.:o:o:o
[LG Optimus L9 P760, P765, P768, P769] kitkitfok:
I have P768 device, Board Version 1.1, Jelly Cream ROM, Can I try?
[LG Optimus L9 P760, P765, P768, P769] amnik:
Should be ok. Although my kernel is built base on P760 and tested on P765, the Jelly Cream can work on all the three versions of L9. It is possibly work on P768. Do you face kernel panic when booting your devices after flash custom kernel?
[LG Optimus L9 P760, P765, P768, P769] kitkitfok:
Yes. I face kernel panic after flash them.

I flash your kernel and no problem. :good:
[Nexus 4 Q&A, Help & Troubleshooting] Salty Wagyu:
I have been having an issue in obtaining a GPS lock on my Nexus 4, Maps can't pinpoint my location with WiFi off and GPS Test shows 22 satellites in view, but 0 in use. But when I clear AGPS data via the GPS Test app (note: I only clear, not re-download new AGPS data), the satellites refresh and is able to lock and use most of them, same for Maps. But this doesn't last, I have to clear AGPS data again the next day in order for GPS to get a lock from the same location (at home).

Obviously this isn't normal behaviour is it? Having to rely on a third-party app to reset AGPS, and so on.

The same behaviour happens on stock 4.3 with no other apps other than the ones included.
[Nexus 4 Q&A, Help & Troubleshooting] Salty Wagyu:
Bump.
[Nexus 4 Q&A, Help & Troubleshooting] coinx7:
SAme probleme here on a xperia go

did you find a solution, or at least, a widget for clearing Adata easily?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] ahegazi:
Upgraded to WM2005. By mistake formated Extended Eom to a small size ( less than required for WM2003SE). Getting ERROR 113 due toEXt Rom size limitation I think. Now can't downgrade to WM2003, nor stay with WM 2005. I still can get to Boat Loader. Please help. Thanks