yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Does anyone know a RSS replacement for Google reader specifically with a scrollable card style widget? I now have a void on my home screen and an emptiness in my heart now that Google has stopped the reader service. I have spent years with this app and have become accustomed to its usage. I'd prefer a flickable one as opposed to one with arrow buttons to scroll. Any help please??? Screens show the widget I was using and the giant hole left behind
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
I use Feedly not sure if it's to your looking but I enjoy using it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
I really do like feedly also. They have a couple widgets, but they are under construction right now and un usable. I can only hope that they add this style.
[Xperia Z General] nnila:
Hi All,

Where can I get the totally stock Sony Xperia Z 4.2.2 ROM from if I want the default Sony Xperience?

Mine has been customised by my carrier so I have no idea when I will get the latest update with it and I dont want to sit around waiting for them for ages.
[Xperia Z General] newtbie:
A quick check with show you this:

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

Not sure whether you can flash this if your phone is locked by carrier
[Xperia Z General] bharat4ever:
Yours is C6602, or C6603? Ether ways there are plenty of stock roms for each.
[Samsung Galaxy Ace Plus S7500] Heartstoler1991:
camera not working in cm 10.1 ... can I use thirdparty camera apps? r they working ?? I never flashed cm 10.1 yet... reply plz
[Samsung Galaxy Ace Plus S7500] Bassel Bakr:
Flash then head to this thread to make your camera works with stock and any third party camera app. FIX CAMERA CM10.1 BY Linq'z Qirls'z Chinese ONLY .!!
[AT&T Samsung Galaxy Note II] DeMi-GoD:
I'm trying to catch someone who's been vandalizing my truck. Hoping I can leave my note 2 on filming my truck all night plugged into the charger. Is there a limit to how long of can make the video?

Sent from my Galaxy S4
[AT&T Samsung Galaxy Note II] Intub8:
It would depend on space available, and video quality. If you are recording average quality to a 64 GB SD card it should record for a few hours.
[AT&T Samsung Galaxy Note II] DeMi-GoD:
Well I just factory reset my whole phone so I have almost full capacity space. Why wouldn't it record a full 8 hours if i have the space?

Sent from my Galaxy S4
[AT&T Samsung Galaxy Note II] DeMi-GoD:
See, lol.

Sent from my Galaxy S4
[AT&T Samsung Galaxy Note II] Intub8:
Nice. It will record until space runs out. Let me figure it out.

---------- Post added at 10:40 PM ---------- Previous post was at 10:35 PM ----------

Here is my findings. Recording 1 minute takes up 125.1mb. This means it will fill up a 32 GB SD card in 4.26 hours which comes out to 4 hours and 16 minutes.
[AT&T Samsung Galaxy Note II] DeMi-GoD:
Oh wow I had never idea it would take up that much space :-\ I was wondering what the numbers ticking down at the bottom right meant.. I appreciate it man

Sent from my Galaxy S4
[AT&T Samsung Galaxy Note II] Eternalty:
If you record at a lower quality you may get more time.
[AT&T Samsung Galaxy Note II] gregsarg:
True....very true...g
[AT&T Samsung Galaxy Note II] Bajanman:
This is correct! But the fact the he'll get more recording space. You give up quality of image, for space. ;)

But you can just use a usb otg, then use a

64gig flash drive which is less expensive:eek: and your good to go!!

You may want to also check this app out because then your screen can b off. While recording :thumbup:

https://play.google.com/store/apps/details?id=com.zeronoiseapps.secretvideorecorder

Just my 2¢®
[AT&T Samsung Galaxy Note II] Eternalty:
Yes don't need to give up too much quality though. I'm sure recording at 720p won't be a big drop in quality. Maybe 480p but best way would be to test it out, OP
[AT&T Samsung Galaxy Note II] LittleRedDot:
So somebody is repeatedly vandalizing your ride? That's not cool at all and I hope you can catch him on tape. I would be linking my note to my laptop via otb and recording at highest resolution because you will need to prove who it is to the coppers, and a fuzzy recording won't do.
[AT&T Samsung Galaxy Note II] Bajanman:
Agree:thumbup::D
[AT&T Samsung Galaxy Note II] jg758p:
Have you looked for a wifi streaming app? Something like that may be better in this situation. Doing a search in the play store revealed a few that could do the trick.

Good luck catching them!
[AT&T Samsung Galaxy Note II] ahmarchi:
Try 480 p... and use 64gb card or 32... just start it as late as u can..... or honestly maybe just buy a pc camera or camera system. .. there are some going around for undr 120 $... lol use it for a few days take it back for a refund lol
[AT&T Samsung Galaxy Note II] TheFletch:
Another choice would be to take a look at Motion Detector in the Play Store. It detects motion, naturally, and might do what you want and not just record everything. My 2 cents

Sent from my Galaxy Note II
[AT&T Samsung Galaxy Note II] DeMi-GoD:
Wow! I had no idea there was such an app... I think this will work perfectly! Thanks so much everyone.

Sent from my Galaxy S4
[AT&T Samsung Galaxy Note II] cdshepherd:
Sit crouched down in the truck with a baseball bat. When criminal arrives beat the living snot out of him. Then use note2 to dial police:thumbup:
[AT&T Samsung Galaxy Note II] rangercaptain:
Another app will take time-lapse pictures. You can set the interval to any increment you need. I used my phone to record eight hours of volunteers building a house in Mexico and it became a four minute video on Youtube.

Lapse It link: https://play.google.com/store/apps/details?id=com.ui.LapseIt

The house build link: http://www.youtube.com/watch?v=5upuu-6D6d4&feature=youtube_gdata_player
[AT&T Samsung Galaxy Note II] Eternalty:
So.... Did you find out who's doing it?
[Ouya Android Development] khanning88:
Unofficial Cyanogenmod 10 (Jellybean 4.1.2) for Ouya - Experimental

​

**MUST READ**

Until Ouya releases a proper method to force the device into a recovery state this is considered risky. If you're ever writing to the boot partition and the power goes out, or you flash a bad kernel, your Ouya could quickly become a shiny new brick.

Because of this, the flashable zip I posted does not contain the boot.img. The boot.img is a separate download which you should use fastboot to boot. I recommend using 'fastboot boot boot.img' until this issue is addressed. Of course this means that every time you reboot your device you will have to force it to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img' (very annoying).

You can use 'fastboot flash boot boot.img' if you want to write the boot.img permanently, but YOU'VE BEEN WARNED. I am in no way responsible for anything that happens to your device.

Right after you install, go into settings and enable adb and adb root access, THIS IS CRUCIAL. You could be locking yourself out if you don't. If you forgot to do this and you find yourself stuck in a bootloop read the section titled 'Stuck in a bootloop' below.

Tested working

Wifi

Bluetooth

Audio

HDMI

Google Play store (Use gapps-jb-20121011-signed.zip)

Ouya Controller

Ethernet (Have to use 'netcfg eth0 up', 'netcfg eth0 dhcp' commands since we have no settings menu)

Expect bugs and please report them. I have not tested this thoroughly.

Make sure you take a backup of your stock Ouya using CWM.

Downloads

cm-10-20130702-UNOFFICIAL-ouya_1_1.zip

0ff08b8c5aaa85e6d091e4e079cdc79c

20130702-boot.img

60b4c4d82dbe317cd14a5deda09b0831

Tips

Disable Battery Icon

- Go to Settings > System > Status Bar > Battery Status Style > Hidden

Disable extra notification drawer items

- Go to Settings > System > Notification drawer > uncheck Airplane mode and Orientation

Set governor to Performance

- Go to Settings > Performance > Processor > CPU governor > PERFORMANCE (check 'Set on boot' to keep changes on reboot)

Stuck in a bootloop

If you ever get in a situation where adb is disabled and you forgot to boot the proper boot.img you might get stuck in a bootloop.

The only option is to try the following to force the ouya to reboot into recovery.

- Power off the ouya.

- Plug in a usb keyboard that has a sysrq or printscreen key

- Power on the ouya, right after the boot animation starts press the sysrq/printscreen + alt + i keys and hold for a second

- Wait a second and press the key combo again, sysrq/printscreen + alt + i, hold for a second

- Repeat this until the device reboots (You should see the boot animation freeze after a few times, this means your getting close :silly:)

- You should end up back in CWM with adb working

Changelog

7/2/2013

- First release

Source

http://github.com/khanning - Device tree

http://github.com/ouya - Kernel source

Thank you

Cyanogenmod Team and all contributers

Everyone here that started the discussion before I got my ouya. Reading through the threads helped point me in the right direction.
[Ouya Android Development] zanderman112:
So interested in trying this, but seems a bit unsafe atm. I'm going to be keeping a watch though, because I bought my Ouya knowing it'd be open to ROMS/etc. I bought it to be a cheap PC for my tv, and the default software doesn't really allow for that.
[Ouya Android Development] BenG321:
Same here. I'll wait for someone braver than me to jump in first. Water looks warm, though!

Sent from my SAMSUNG-SGH-I727
[Ouya Android Development] mybook4:
Devs, I propose the following to get rid of the potential brick risk:

Since we can't get into recovery manually (via HW buttons), let's reverse the role of SOS (recovery) and LNX (kernel). Since LNX is the booting kernel partition, let's flash recovery there and flash the kernel to the recovery partition. I believe we could do this by modifying the fstab and having our updater-scripts flash to the appropriate partitions.

From a cold start, a user will enter recovery (a minor inconvenience for safety). Depending on how we modify the recovery.fstab, getting to the ROM could be as simple as pressing power twice (recovery does a reboot system now and its fstab has the system actually reboot to the recovery partition, which is the ROM's kernel).

Definitely not straightforward, but should prevent bricks. Thoughts?
[Ouya Android Development] professorpoptart:
It sounds almost to simple to work! lol

Really though, I see no reason why this would not work... even without hardware buttons, its just selecting "reboot recovery" from the cwm menu.

Might need a discussion around how this would effect the sysrq+i recovery... I believe we would be safe as (from what i can tell) it doesn't boot to the SOS mmcblk directly, it just go's to whatever "recovery" is.

I already have my second ouya on the way so I have no issues testing it out.
[Ouya Android Development] Asadullah:
I think it would be easiest for ouya corp to give us the boot loader source code and let us add I'll those features in ourselves
[Ouya Android Development] elmerohueso:
This is awesome. Maybe you should add a link to this on the OUYA subreddit. Hopefully more exposure makes it more obvious to OUYA how much we need easy access to recovery.

And if more exposure means more noobs bricking their console, then they'll all be contacting OUYA to fix it (since it's not explicitly excluded from the warranty), and that might get them on the ball to release stuff faster.
[Ouya Android Development] DivinityCycle:
This should be fine. One of the things people may not know is that the Ouya is basically an "always on" device which is generally rarely shut down, so a cold boot is not a frequent thing. As a result, making a cold boot slightly less convenient isn't a real issue IMO, particularly as this will ONLY effect users who have opted to flash CWM and ROMs and stuff on their Ouya.

However, making such an extensive modification would mean we better be damn sure the OTA updates are prevented. I can easily imagine an OTA update coming along and breaking everything when it fails to properly update the device upon encountering the non-standard layout. Its one of those "that shouldn't happen" scenarios, but why chance it if we don't have to?
[Ouya Android Development] b00sted:
I am not too active on these parts anymore but wanted to post thank you for this and once they got proper recovery in place incase I bif my only media box I have for my tv I will give this a go!. ty again for all the work you have done.
[Ouya Android Development] HellRa1SeR:
This is what eventually will be on my OUYA, probably a dual boot. The reason being that a lot of games on the play store nowadays have controller support. So I can have a huge catalog of games through there. Also, not to forget movies, music etc.

And whenever I wish to play OUYA exclusive games I could hop back on to the OUYA Rom.

Best of both worlds. :D

Great work devs.
[Ouya Android Development] zanderman112:
So, if I were to install this, permanently, the instructions would be as follows?

Boot into recovery using 'adb reboot recovery'

Flash zip

Reboot to the bootloader using 'adb reboot bootloader'

Use 'fastboot flash boot boot.img' to flash the boot.img permanently.

Reboot, done?
[Ouya Android Development] jmhalder:
The OP suggests that you don't do that quite yet, rather just boot into recovery, flash the zip, and use fastboot to boot the proper boot.img every time... This was you should always have the stock kernel installed on the /boot partition, and there are ways to get back to the recovery if you mess something up. So use 'fastboot boot boot.img' instead. If the kernel can't boot for some reason, currently you can use alt-sysrq-i to get back to recovery, if you mess up the boot partition, you can't, and you'll be completely bricked.
[Ouya Android Development] BUS DR1V3R:
I hate to be the one to ask this, but could someone provide step-by-step instructions? I haven't had a reason to use ADB very much but I would very much like to enjoy my Play Store games that have already been purchased on my Ouya. Thanks in advance for anyone willing to take the time to explain this process a little better. :good:

Also, should we wipe anything?
[Ouya Android Development] zondajag:
Is CM10.1 on the horizon at all? What wouldn't work?
[Ouya Android Development] toxicbubbles:
Good work man, oh so tempted but my kids use this for watching vids and so will keep my fingers crossed you find a way to make this more permanent. Keep up the good work
[Ouya Android Development] BUS DR1V3R:
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.

Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.
[Ouya Android Development] super jay:
are you in fastboot?
[Ouya Android Development] BUS DR1V3R:
I am not entirely sure. The OP says to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img'. This is what I was trying to do, and I found that if I leave the spinning logo up long enough I can reboot bootloader, but when I try to fastboot the boot.img it just says <Waiting on device>.
[Ouya Android Development] Asadullah:
I'm running it right now with really no issues. What I did was reboot to recovery did a factory reset then formatted system, data and cache. Then installed cm10 and then rebooted to bootloader and flashed the boot.img and did a reset. After that I made it into system and looked around all happy then did a reboot recovery and flashed gapps.
[Ouya Android Development] super jay:
Edit: didn't read closely enough sorry
[AT&T, Rogers HTC One X, Telstra One XL] htcfan85:
I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.

My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.

So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.

I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.

Please, I would really, really appreciate any help!
[AT&T, Rogers HTC One X, Telstra One XL] hi_cannon:
I would run the 3.18 RUU (which you can do in fastboot).
[AT&T, Rogers HTC One X, Telstra One XL] Venomtester:
Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.
[AT&T, Rogers HTC One X, Telstra One XL] htcfan85:
I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?
[AT&T, Rogers HTC One X, Telstra One XL] Venomtester:
So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
[AT&T, Rogers HTC One X, Telstra One XL] htcfan85:
Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
[AT&T, Rogers HTC One X, Telstra One XL] Venomtester:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
[AT&T, Rogers HTC One X, Telstra One XL] htcfan85:
This is what I'm worried about:

SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.

http://xdaforums.com/showthread.php?t=2191477
[AT&T, Rogers HTC One X, Telstra One XL] Venomtester:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
[AT&T, Rogers HTC One X, Telstra One XL] htcfan85:
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.

EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.
[AT&T, Rogers HTC One X, Telstra One XL] Venomtester:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
[AT&T, Rogers HTC One X, Telstra One XL] kotchishm:
Second Flash GUI....works like a charm
[MDA, XDA, 1010 Software Upgrading] McNugget:
Hi there,

I tried to upgrade to SER1.2 and did everything like discribed in the readme file. Then when I started the upgrade process the XDA drew the status bar and halted.

My Programm A stopt and nothing happens. After some time the Programm A thows an error message and said that I have to reboot the XDA and trie again. I did exactly that. Every time I turn the XDA on after a Reset, it draws the statusbar again and nothing happens.

I tried the boot loader. That works!

But I was not intelligent enough to copy my Backup onto my SD Card. So I'm down at the moment.

Any ideas?

Geets,

Timo
[MDA, XDA, 1010 Software Upgrading] McNugget:
I'm working at the problem at this moment. XDATools in conection with my SD-Card hopefully solves my Problem. The System flashes now.
[MDA, XDA, 1010 Software Upgrading] McNugget:
Well system is back to life again :P
[Sprint LG Optimus G] samsungepicgeek:
Can anyone port this lockscreen to our AOSP roms, preferably Vanilla Root Box? It just looks too sick. http://xdaforums.com/showthread.php?t=2296082
[Sprint LG Optimus G] BMP7777:
I am working on it this weekend but no promises. Seems like it should be fairly straightforward, but that means nothing with an LGOG.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] E The Magnificent:
I ask this because when I installed flash player apk on my S3 it worked but on the GS4 browser it don't work. So I'm wondering if I download the gs3 browser will it work on this phone? Yes I'm aware of 3rd party browsers but I'm a stock browser dude
[Samsung Galaxy Ace Plus S7500] Heartstoler1991:
Is there any custom ROM available which is based on 2.3.6 gingerbread and in About phone it is showing 4.0.4 or 4.1.1 .. ?? like in galaxy y many ROMs r based on 2.3.6 gingerbread.... but they only changed android version to 4.1.1 ... in About phone ... reply someone
[Samsung Galaxy Ace Plus S7500] kk9999gada:
You can change it yourself from build.prop just change 2.3.6 to 4.1.1 and so on. It is there in sixth or seventh line in build.prop.
[Samsung Galaxy Ace Plus S7500] vickyg.coolest:
Normal Method Done Via Root Explorer

1, Open "Root Explorer" and mount R/W.

2, Go to "system" and you will find there is a file name "build.prop".

3, Right click (By holding at the file) and there is menu pop out.

4, Scroll down and select edit in Text Editor.

Once in build.prop you can edit the following things:

-edit Android Version by locating ro.build.version.release= and changing the current Build Version.

- Edit your Model # by locating ro.product.model= and changing your model #

- change your product brand by locating ro.product.brand=

:good:

WARNING

Please Note that if you change the product brand, the name MUST be in ALL LOWERCASE LETTERS!!!

editing build.prop in wrong way may give you bootloop so do it with caution and make a nandroid backup!!
[Samsung Galaxy Ace Plus S7500] Heartstoler1991:
than a lot .... god bless u
[Samsung Galaxy Ace Plus S7500] vickyg.coolest:
no need to say thanks !!(just press it :P )

god bless us all :P