yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] DirgeExtinction:
Blame app developers.
[Nexus 4 General] kien:
I bought the Nexus because of the cost and design. If it was the same price made by someone else with a skinned version of android I still would have bought it, rooted and flashed a different ROM.

I like to be up to date but am happy waiting for a stable release with features I like. Whats better for you might not be for everyone else.
[Nexus 4 General] Michealtbh:
Some apps absolutely have to run constantly, such as my vpn app
[Nexus 4 General] anirudh412:
If you bought a nexus device and aren't ecstatic and crazy happy with every single update, no matter how small it is, then something is wrong with you :silly:

And by the way, it's ok if you are patient and can wait. Let the rest of us mortals make as many threads as we like. It's not like you are forced to go through every single one of them

---------- Post added at 03:37 AM ---------- Previous post was at 03:31 AM ----------

Not one single issue with Cataclysm 4.3+Franco r173 here
[Nexus 4 General] voodooline:
I noticed it to. Crisper or something.
[Nexus 4 General] kipue:
I'd say that what makes sense is to wait a little and keep reading the horror stories of some unlucky early adopters, haha!
[Nexus 4 General] daglesj:
Must admit I'm in no hurry. Plus the issue is that I'm rooted, custom kernel blah blah blah so I have to wait for all the ancillary folks and their apps to catch up to 4.3 compatability.

To be honest I might just revert back to total stock/unrooted. The only real boon of being rooted for me was adjusting the screen colours.

If I go back to unrooted I can also use the handy banking apps again.

Decisions decisions.
[Nexus 4 General] frigidazzi:
Tried it for a day, but missed you many features from aokp so I went back. I did go to 4.3 on my n7 though. Made a lot of difference on that one. Not so much for my n4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Svtsilversnake:
Im new here so bear with me. I did a search but couldnt find an answer. I flashed the kt747 kernal and it seems to work fine. However it seemed to create a freezing issue when I had setcpu installed. Possibly because it came with its own tuning app. My problem is that when I enable the over clock steps it will keep my max at 2.1ghz but the about ten minuts later chanfes it back to 1512ghz. Yet the slider will still show to be set at the max of 2.1ghz. So what gives? With the govener set to performan it should be locked at the max set value correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXFl4sh:
Can you try a different frequency and post the results? Try 1800, which I use. You can also try locking the frequencies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Svtsilversnake:
I re flashed it earlier today and it seems to be better but im not sure yet. Even with it at 2.1 ghz my keyboard is slow. But it may just be the tapatalk app. Using setcpu is faster at selecting frequencys but they dont seem to stick. Ill try 1800. Im assuming you use the same kernal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXFl4sh:
I am on this kernel but on liquid smooth
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Svtsilversnake:
Got a quick question for you then. I looked around and maybe I dont know what to search for specifically but where do I find the stock kernal file if I want to reflash it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DMF1977:
What ROM are u running? Just dirty flash the ROM and u will get stock kernel back...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Svtsilversnake:
Its the stock rom. So only a ditry flash will restore the kernal to stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flatherskevin:
your keyboard is slow because you have underclocked it so low. try something in the high 200's
[Galaxy S 4 Q&A, Help & Troubleshooting] munmun:
Is it because of the different quad-cores?? Will i9500 ever get miui??
[Galaxy S 4 Q&A, Help & Troubleshooting] Oniyuri:
It's something like that. Exynos isn't as open as Qualcomm is and Samsung (AFAIK) has no intentions of releasing the sources/documentation that the devs need to make fully functional custom ROMs.
[Galaxy S 4 Q&A, Help & Troubleshooting] munmun:
Thanks for replying.

So that means we won't be able to rum miui on i9500??
[Nexus 7 (2013) Themes and Apps] Nexus11:
Dose anyway know of any video players with 4.3 support?
[Nexus 7 (2013) Themes and Apps] Superpopsss:
Vplayer
[Nexus 7 (2013) Themes and Apps] DonutRaider:
The only one I'm aware of with proper custom codec support for DTS output is DicePlayer.
[Nexus 7 (2013) Themes and Apps] spotmark:
I'm using BSplayer until MX gets updated.

Edit-Archos player has been updated, and is now working.
[Nexus 7 (2013) Themes and Apps] kayone73:
Player Pro app plays video fine with 4.3 but my current version of MX Player does not.
[Nexus 7 (2013) Themes and Apps] slyr114:
im using the vlc beta app until mx player is updated for 4.3 properly. The testing build of mx player works too but is a bit unstable.
[Nexus 7 (2013) Themes and Apps] ...Awesome...:
Thread Closed!!!

Since there is already a duplicated thread...

http://xdaforums.com/showthread.php?t=2384188
[Galaxy Camera Android Development] twistedumbrella:
https://github.com/StarKissed/ek-gc100_recovery

This recovery was made using the EK-GC110 recovery.img ramdisk from the latest firmware release. The CWM Touch 6.0.3.2 is from a Samsung Galaxy SGS3 (Same board), modified with the custom kernel for the EK-GC (stripped version from this forum). The original recovery was used to provide the corrected init and fatal values, but all other aspects are relatively identical to the SGS3.

The recovery functions work, and appear fully functional. Keep in mind this is still in the testing phase. Work is being done to rebuild the necessary device configuration files based on information about the EK-GC and SGS3. The only aspect untested is the sdcard formatting options.

StarKissed Galaxy Cam Recoveries

This brings custom recovery to the Galaxy Camera, which is accessible by holding the zoom toggle to the right (red indicator should be on +) and pressing the power button. The difference between recovery and download mode is whether or not the shutter button is also held. Keeping the shutter button pressed will result in launching the Odin download mode.
[Galaxy Camera Android Development] RavenY2K3:
It gets better ;)

Any idea if it works on the EK-GC100 (3G and Wi-Fi version) ?
[Galaxy Camera Android Development] twistedumbrella:
Should work on all variants. The radio isn't called by recovery so I see no reason it wouldn't.
[Galaxy Camera Android Development] RavenY2K3:
I was thinking more along the lines of the partition tables, I wasn't sure whether there were differences in that respect between devices and, whether it makes a difference even if there was.
[Galaxy Camera Android Development] twistedumbrella:
If you have a root file browser, they are in /dev/block/platform/dw_mmc/by-name and the partition names should list where they link.

System is p9, boot p5, data p13, recovery p6

If they don't match, it would only be calling the by-name links instead of specific numbers. I avoided that for extra stability, but it would still work properly. I use the by-name for mounts and flashing in the zips already.
[Galaxy Camera Android Development] GriffinSauce:
Hey I can't get this to flash.. stuck at NAND write when I use the gz and Odin says the MD5 is incorrect if I unpack first.

Any help?
[Galaxy Camera Android Development] twistedumbrella:
Download the tar version without the md5. Once the md5 is written to the file it can't be removed, but goo provides md5s to verify locally. I've tried md5 -r and that didnt work, but apparently neither did the homebrew md5sum
[Galaxy Camera Android Development] GriffinSauce:
I see only .img and .gz files. Tried unzipping and removing the MD5 check, no dice.

Odin hangs at "NAND write" now.. Luckily no problems after resetting the device (no cwm though ;) )
[Galaxy Camera Android Development] twistedumbrella:
That's what I get for trusting my script. It missed copying the basic tar to the folder to upload. It should be uploaded shortly. That one should solve it.
[Galaxy Camera Android Development] GriffinSauce:
Argh, that didn't work either so I took a good hard look and I see I have an EK-GC100 ... :rolleyes:

Sorry for wasting your time so far. :(

Do you think it is possible to make it compatible? Can I supply my stock recovery for that?
[Galaxy Camera Android Development] twistedumbrella:
It should have been already but with the stock one I can make sure it will be
[Galaxy Camera Android Development] GriffinSauce:
https://www.dropbox.com/s/osyk8p05kjcicjg/recovery.img

This is the stock recovery of my device. Thanks for taking the trouble!
[Galaxy Camera Android Development] twistedumbrella:
I didn't forget about you. Tomorrow I should be able to get something together that will work.
[Galaxy Camera Android Development] twistedumbrella:
Alright, I took the stock recovery that was posted and used the kernel image and modules from that, tweaked the partition tables a little more, and hopefully it should now work. Samsung is weird. Some have an internal_sd and external_sd, some have sdcard and this extSDCard, some have sdcard and sdcard1. No wonder apps always have issues with trying to use the card.
[Galaxy Camera Android Development] GriffinSauce:
Thanks again!

Still no go. I tried recovery.08-13-2013_08.42.tar and recovery.08-13-2013_08.42.tar.md5. Still halting at "NAND Write Start!"

Tried with Odin v3.07 and 1.3. Also did flash a stock rom via Odin the other day, so it should work..

Could there be some write protection on the recovery?
[Galaxy Camera Android Development] twistedumbrella:
There shouldn't be. I don't use Odin, though. I have a Mac, so I have a compiled version of the Heimdall or whatever that one is. The original flash was done with Odin, though. I wonder if its a lock from the service provider. Let me see if I can somehow get a proper md5 attached. That may help.
[Galaxy Camera Android Development] GriffinSauce:
Ah but I can try Heimdall too. I'll try tonight. :)
[Galaxy Camera Android Development] twistedumbrella:
Alright. At least then I can try to zero in on the issue.
[Galaxy Camera Android Development] Delux9364:
I fixed the problem.

Just unzip and flash this through Odin.

Reboot with power + zoom+

You're in CWM recovery, enjoy! :D
[Galaxy Camera Android Development] twistedumbrella:
What problem? What model? What was done? If it's anything more than signing with the right md5, you may want to submit a pull request.
[Galaxy Camera Android Development] Delux9364:
The recovery.img is untouched (thaylt's the last recovery.img you compiled). I just let the image be flashable through odin w/o keep failing.

Alla credits are tours, man! ;)

Btw model on which it works: EK-GC100
[Galaxy Camera Android Development] twistedumbrella:
Credit doesn't matter when it's a modified version of the Galaxy SIII recovery anyway. What matters is not making more images that need to be modified when it can be done right the first time.

Edit: seems its the tar command not being compatible, not only the md5. I should have it worked out for future compiles shortly.
[Galaxy Camera Android Development] Delux9364:
OK so... Until you make a fully-working flashable recovery I'll keep using the one I posted above! :)
[Galaxy Camera Android Development] twistedumbrella:
You should only need to flash it once per recovery version. The updates were published and should show up shortly. The source should already produce working recoveries from Linux, but I won't push the changes to Mac compile until someone confirms that changing the tar command fixed the issue.
[Galaxy Camera Android Development] GriffinSauce:
YES!! Sorry for the late reply, this works!

Heimdall didn't work with the original files either. Anyway, I have CWM now and can do backups and screw around without fear :)

Thanks so much both of you, very awesome!
[Galaxy Camera Android Development] twistedumbrella:
I have a feeling the tar command was corrupted when I went to add it to the script because I had the Linux command in the Mac section.

Over the next few days I will start releasing the mods and packages I've been working on. Currently the deodex is a 1:1 replacement of files to work with almost any region, but I am working on being able to do the phone/sms mod and reboot without having to have a specific build or lose the sound menu options.
[Galaxy Camera Android Development] Jiggity Janx:
Update right from the source: http://www.samsung.com/us/photography/digital-cameras/EK-GC120BKAVZW-specs

Verizon model uses MDM chipset vice Exynos. Won't this affect trying to use all the same source for kernels and recoveries?!? I hope not...

EDIT from another thread but relevant:

Old: I have to ask because I can't seem to find the answer to this but I thought I caught somewhere that at least the Verizon GC120 uses an MDM qualcomm chipset vs the Exynos 4412. Is that true and if so wouldn't it affect this? If not I'm happy to be proven wrong but couldn't come up with a solid answer.

*I'm hopefully picking up a Verizon variant of this soon but likely won't if I can't at least use recovery. If I do I can provide you whatever files you would need from it for this and/or the kernel. Thanks for all your work either way!
[Galaxy Camera Android Development] twistedumbrella:
That would make things a little different, but only in respect to getting a different kernel into the recovery for that one. It should be an easy fix.
[Galaxy Camera Android Development] Jiggity Janx:
That sounds good. Think I will pick one up soon to give it a try.

Problem I see is I dont know if an updated verizon version can be rooted to do any of what I want. Saw a thread about that somewhere.
[Galaxy Camera Android Development] Fallen_Knight:
op did you update the recoveries in your goo page??? im using gc100...
[Galaxy Camera Android Development] twistedumbrella:
What do you mean? After the fixes for Odin? If so, then yes. Just in case, I will run a quick build right now.
[Galaxy Camera Android Development] Fallen_Knight:
I used the one mentioned by other member..so is odin fix implemented already? One question.. what are the bug?
[Galaxy Camera Android Development] manekineko:
So this would be expected to work on an EK-KC120L right?

That's a Korean LTE Galaxy Camera, which uses an Exynos 4412 according to CPU-Z.
[Galaxy Camera Android Development] twistedumbrella:
Yes. There is always a possibility it won't but it is very minimal.
[Galaxy Camera Android Development] manekineko:
No go on my EK-KC120L.

When I tried the files in the OP, they were still on the version with the bad MD5 sum - recovery.09-08-2013_09.05.tar.md5 did not work for me.

Instead, I used the file from this post, which seemed to be valid in ODIN: http://xdaforums.com/showpost.php?p=45048758&postcount=19

Restarted into the bootloader by shutting down and then starting the phone while holding zoom- and power.

Connected via ODIN, and flashed the recovery, and according to ODIN the flash completed successfully.

However, upon booting into recovery, it was still the stock Android system recovery.

Any ideas on what's going on? I wonder if my variant might have a locked bootloader?

Edit:

So it turns out that the recovery is somehow being flashed and then flashed back to stock. If after flashing CWM, I immediately reboot to recovery without allowing it to boot system first, then it does boot into CWM.

However, there are a number of mount errors it immediately complains about (for /cache/recovery/command, /cache/recovery/log, and /cache/recovery/last_log). Viewing the logs under advanced also shows warnings that it failed to mount /dev/block/mmcblk0p8, as well as a variety of other informational messages.

The first time I allow it to get into the boot animation, though, the recovery reverts to stock. There is no option on rebooting in CWM to disable stock recovery flash.

Edit 2:

Based on searching on XDA, I've determined the problem is likely that /etc/install-recovery.sh is rewriting the stock recovery on every boot. (No idea what the problem is with the errors mounting in CWM.) However, in order to work around install-recovery, I'd need root to disable it. However, if I can't get a clean image prior to rooting, then I'll have no way to flash back to perfect stock in the event of a firmware update, since Samsung doesn't seem to have released files for this variant. Guess I'm giving this up for now.
[Galaxy Camera Android Development] twistedumbrella:
There should be a way to backup the images from the device without root. In fastboot it's possible, so Odin should have some variation. Worst case, flash and boot straight to CWM, run the backup, then root.
[Galaxy Camera Android Development] Jiggity Janx:
If the bootloader is locked making changes to the recovery.sh wont stick/work so root wont help with that. Otherwise to do the above its likely framaroot will root the device and unroot if required later.

Also its possible the /system from the 120s I posted in the verizon thread can get you back to stock.
[Galaxy Camera Android Development] twistedumbrella:
recovery.sh is in the system. You can root a phone with a locked bootloader. If you mean what I said by from above, it was referring to the initial comment that flashing recovery works but doesn't stick. Is your build Verizon? Because returning to stock refers to returning to the original factory condition, not flashing an unmodified /system folder from another region.
[Galaxy Camera Android Development] Jiggity Janx:
Yes you can root a phone with a locked bootloader but that does not mean you can just overwrite/remove install-recovery.sh to allow to install and keep a non stock recovery.

EDIT: You can edit the .sh but an alternate recovery wouldnt be signed so wouldnt come up with a locked bootloader. So imo because they could boot to cwm their bootloader likely isnt locked.

EDIT: Unfortunately the closest I fiound to verizon was the 120s I mentioned.

But I have seen instances where updates were tricked into believing a device was stock by using /system from another device. Have to find where I saw that one...

---------- Post added at 06:29 PM ---------- Previous post was at 05:46 PM ----------

I am going to try all this tonight with the verizon one. Wanted to last night but killed my battery finding root (and with the verizon demo app that I dont want to stop until I am sure it wont break it).
[Galaxy Camera Android Development] twistedumbrella:
Look first, post second. Stop guessing.
[Galaxy Camera Android Development] Jiggity Janx:
My first set of posts was while on the move. Didnt feel I had to expound on what I was typing until I had a minute. Nothing in it was going to negatively impact anyone. Would appreciate if you accepted others might be knowledgable and helpful.
[Galaxy Camera Android Development] twistedumbrella:
This thread will be closed until all three devices have working recoveries. That way, all the research and guesswork doesn't have to cloud up the thread for downloading and using them.
[Nexus 4 Accessories] noobletsausecakebbq:
http://www.ebay.ca/itm/XGear-EXOSki...ll_Phone_PDA_Cases&hash=item4ac2b78b68&_uhb=1

How would I go about putting a screen protector on with this?
[Nexus 4 Accessories] anirudh412:
Though I don't know how well it would work, but I would think would need to put the SP first and then the front skin. But I see a problem, if its a dry SP, then it won't go all over the edge. That might cause problems with the fit of the skin itself. Are you dead set on using the front skin?

Oh and don't buy it from there. XGEAR has a 60% off deal on the EXOSkin on their website right now

EDIT: correction, they had the promo for the weekend only. You could still try and see if it works. The code is EXOIPNEX4IPD2

EDIT 2: looks like it expired
[Nexus 4 Accessories] AlphaKoi:
Quoting myself.....the answer is VERY CAREFULLY. honestly best idea is tempered glass protector for front. Its difficult otherwise and probably not going to come out looking "perfect"
[Samsung Galaxy S Relay 4G] xdaforo:
hello guys, im asking for opinion in several subforums for the devices with qwerty kb and touchscreen

Are you happy with this phone?

I'm hesitating particularly with this one due to the lack of development and support, which its doing me reluctant to consider it, as for the stratosphere ii

These are my options.

Anything important i should know about this device?

In your opinion, should it work in spain?
[Samsung Galaxy S Relay 4G] Braccoz:
it will work in spain.

it's a nice device, the worst thing about it is the pentile matrix display imho. out of all the ones you listed, it's the best.

the only qwerty slider that is better than relay is the photon Q but it requires hardware modifications to work with SIMs

last but not least, the relay has an *amazing* dev team. if you however expect to have the same amount of roms as more popular phones like sgs3/4, well, you're out of luck with any qwerty slider then
[Samsung Galaxy S Relay 4G] xdaforo:
hello

thanx for your answer. I didnt know about the pentile matrix display. I've been reading about its pros and cons.

and yeah i read about the modifications that you have to do to the phothon Q as well. It comes with attached sim, or something like that.

well, im kinda new over here and also new with android stuff. I was a nokia n95 user till recently. But if i compare the movement in this subforum with something like the one for the captivate glide or this thread for the se xperia pro thread, it seems to be a bit slow. Still more options here than the offered ones for the stratosphere 2. And yeah it seems to be one of the best mobiles of its kind.

I take note of what u said. Thank you!
[HTC EVO 3D] tokurugur:
my android s-on and unlocked. i tried to setup a cyanogenmod rom but its can not setup a s-on device so its stuck in bootloop. then tried some fixes but can't solve problem also when i try to acces recovery on hboot its jump into boot then stuck.

how do i fix ?
[HTC EVO 3D] duscdragon:
Most serious bootloops can be fixed my simply installing a new boot.img through fastboot. Here is a link on how to do that:

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

After you do that. you can try installing a new recovery through the same process. Instead of flash boot.img, flash recovery.img. That should fix your problem. If you STILL keep getting bootloop, you now have access to recovery and can do a factory reset. Hope this helps! you can get the boot and recovery image from a stock EVO 3D Rom.
[HTC EVO 3D] tokurugur:
thanks your solution but i have already tried that but did not fix. is there any way to do recovery process via computer.because i can not access recovery
[HTC EVO 3D] duscdragon:
First of all, you don't need to access recovery to flash fastboot. What you need is the bootloader, which you can access by holding the volume down and power key. But, if what you're trying to say is that you can't access even the bootloader, then one of the limited choices is to download the EVO 3D RUU and flash a stock this way. If this doesn't work, you are one of 2 choices: adb-retarded or screwed. There is piratically no other way, than the choices listed. (IDK, maybe you can try to flash S-OFF with Jbear, and in the process fix your phone. I mean you have nothing to lose :))
[HTC EVO 3D] sixty9fordkiller:
x 2. Also, (and just out of curiosity) did you happen to accidentally leave a PG86IMG.zip file inside your SD card? That could cause something like what you're experiencing too. If so, take the SD Card out, place it in a PC with a card reader, erase (or rename) the "PG86IMG.zip" file, reinsert the SD Card and battery, hold down the VOLUME DOWN and POWER button and see if you can get into bootloader/recover/fastboot menu