yashsingh1/xdaforums huggingface dataset:
[One (M7) General] mettleh3d:
http://www.androidcentral.com/pre-release-android-43-update-htc-one-leaks

Discuss

"Firstly, it's now possible to use your own music for video highlight reels, and Sense will sync picture changes to the beat of the track."
[One (M7) General] mettleh3d:
Oops seems like I'm way late. Can delete.

Sent from my Nexus 7
[One (M7) General] Ovy13:
By the end of September! Which probably means February for Verizon.
[One (M7) General] xxquicksh0txx:
Most likely February 2015 for Verizon.
[One (M7) General] Theshawty:
Implying it'll ever happen ;)
[One (M7) General] Dark Fable:
International Business Times

Android 4.3 (3.09.401.1) Leaked for HTC One M7 [Install via Maximus HD ROM]

http://www.ibtimes.co.uk/articles/5...id43-3094011-jellybean-maximushd.htm?fs=f5dc6

Came across this in my blinkfeed.
[One (M7) General] pandaball:
Thread closed. Old news ;)
[General Accessories] jaythemagician:
Just been browsing around and found this-complete bargain to me,just ordered one

http://www.emartbuy.com/uk/catalog/item/miscl/itemDetail.aspx?itemId=377
[General Accessories] sh500:
The 1 gb cards are dramatically coming down in price as the 2 gb enter the mass market.

Just ordered a 2gb for £65.
[General Accessories] findus:
Aren't there problems with certain 1GB/2GB cards working on our devices? It's the reason I have stuck to my 512MB, but if this card works, please let me know!

Thanks for your help,

Fin
[General Accessories] sh500:
I recently sold my 1 GB SD Sandisk and it worked fine on the I-mate JAM.

The seller of the 2 GB assures me that these have been tested on the JAM too.

I think some people are having trouble in the PPCs recognising the 2 GB though.
[Ouya Q&A, Help & Troubleshooting] Pommes_Schranke:
I have tried two different USB keyboards (Cherry evolution stream XT, Cherry G80-3000) but none of them seems to work.

Both keyboards are working when connected to a pc. The OUYA usb port recognizes my mouse. So I guess it has to be a software problem.

Anybody else encoutering similar problems or having an idea to solve this issue?

I didn't find a single thread where a corded USB keyboard didn't work. I have no other keyboard to test :(.
[Ouya Q&A, Help & Troubleshooting] TadeoNYC:
Go to advanced settings and make sure in language and input that hardware keyboard is on.
[Ouya Q&A, Help & Troubleshooting] Pommes_Schranke:
In advanced settings there's only the ouya keyboard. I cannot switch the input method.
[Ouya Q&A, Help & Troubleshooting] TadeoNYC:
Even with the keyboard attached? Do you connect the keyboard before booting up?

I've been using the Asus keyboard from my pc with no issues. When connected there is always the option to enable and disable it.
[Ouya Q&A, Help & Troubleshooting] HT123:
I have had problems in this area as well. For me pulling the power, plugging in the keyboard, and then putting the power back seems to work a lot of the time. Sometimes it is just a matter of doing it a bunch of time until the keyboard is finally recognized. To me, this issue speaks to the build quality and software quality of the Ouya in general. Stuff like this makes the Ouya pain in the a** for the masses.
[Ouya Q&A, Help & Troubleshooting] TadeoNYC:
What about using the power button to initiate a real shut down before attaching the keyboard.

It seems the OUYA is not built using parts from a single manufacturer and that has a lot to do with inconsistent performance.
[Ouya Q&A, Help & Troubleshooting] Pommes_Schranke:
I tried everything mentioned in this thread at least a few times with the two different keyboards with no effect.

I pulled the cord, plugged both keyboards in and turned it on. Powered it off with the hardware button and pluged the keyboard in. Searched the options for any signs of a keyboard that is connected but just not activated.

I also tried different builts (there was an auto update). None seems to work.

This box is a pain in the a%&. I seem to have a very *****y ouya. XBMC is not working quite well too.
[Ouya Q&A, Help & Troubleshooting] HT123:
Using a hub

Are you using a USB hub?
[Ouya Q&A, Help & Troubleshooting] Pommes_Schranke:
No. I tried using a hub as a fix but it didn't help.

I'm absolutely clueless.

I guess installing a custom rom or a bootloader is no option without a working keyboard. The OUYA seems to be a complete waste of time and money so far. Only crap games, worst "store"/rom ever, loud fan, controller with input lag and XBMC not working properly. Unfortunately people seem to have recognized how bad this thing is, where I live the resell value is free falling.
[Ouya Q&A, Help & Troubleshooting] HT123:
Does it work in recovery? Does the cap lock light come on when you press the cap lock button?
[Ouya Q&A, Help & Troubleshooting] Pommes_Schranke:
No and no :(.

Ouya and keyboard are acting like there is no connection at all. But when I plug in any pc mouse everything is working fine.
[Ouya Q&A, Help & Troubleshooting] HT123:
I am at a loss as well. I'm not sure how attached you are to your current install on the OUYA but you could try to sideload the latest OTA. I am pretty sure you can do all that without a USB keyboard attached via ADB. You could also fastboot CWM and see if it is recognized then. Just a couple shot in the dark idea but as if a mouse works, the USB port must be working.
[Ouya Q&A, Help & Troubleshooting] Pommes_Schranke:
I borrowed a logitech keyboard from a friend and it's working like a charm.

The problem seems to be "cherry only".

That sucks. Now I have to buy a new keyboard for this crapcube :D since my friend needs his keyboard.

Thanks for the advices to everyone.
[Nexus 7 Q&A, Help & Troubleshooting] budapestkave:
Hi guys,

Since the 4.3 update, I have only 6GB of internal space on my Nexus 7 device, even though I have the 16GB version :(

Do you guys now what can be the source of this problem and how can I solve it?

Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] :
http://xdaforums.com/showthread.php?t=2382756
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
Total space 6gb, tells me the partition size is wrong. What would cause that, I dunno. I'd have to guess you played with more than just updating to 4.3. Anymore more to tell us?
[Nexus 7 Q&A, Help & Troubleshooting] spitfire2425:
Mine did this. I ended up formatting everything and flashing a new ROM.

Sent from my HTC One
[Nexus 7 Q&A, Help & Troubleshooting] RodMyers:
How did you keep everything you needed?
[Nexus 7 Q&A, Help & Troubleshooting] lars1216:
Backup to PC?
[Nexus 7 Q&A, Help & Troubleshooting] RodMyers:
Using adp?
[Nexus 7 Q&A, Help & Troubleshooting] lars1216:
No backup all stuff first than completely reset and flash a new rom. (backing up just like you normally would via MTP)
[Nexus 7 Q&A, Help & Troubleshooting] spitfire2425:
I had to pull everything I wanted to keep then formatted every partition clockwork had to offer, flashed a ROM through adb sideload then moved it all back.

Sent from my HTC One
[Nexus 7 Q&A, Help & Troubleshooting] szabadgy:
it looks like you bought a 8gb version
[Nexus 7 Q&A, Help & Troubleshooting] absinthesummer:
Well, I'm sure op knows if it's an 8 or 16gb tablet lol. Mine is a 32gb tablet, and had been for over a year. When I upgraded to 4.4.4, mine did the same thing, it showed 6gb free, usable space. I formatted & reflashed everything but it didn't help.

What did help was locking & unlocking the bootloader. I also updated the bootloader but that wasn't necessary. For some reason, re-locking & then unlocking the bootloader reset the available computed space. I'd recommend anyone facing a similar problem on a nexus 7 after an update try the same thing, because for some unknown reason, the device defaults to thinking & reporting it's an 8gb tablet when it's really not.
[Sony Xperia ZL] razz2503:
i forget back up chargemon, after installed dual recovery and uninstalled it, but accidently deleted chargemon.stock,

i need chargemon from stock .244 in bin for offline charging,

can some one upload it?

(to make offline charging back work on stock kernel, only chargemon in bin which i need, doesnt it?)
[Sony Xperia ZL] Crash338:
Here is mine from stock .244
[Sony Xperia ZL] razz2503:
thanks :)

sorry online from opera mini hard to hit thanks button, maybe tomorrow
[Samsung Galaxy S 4 Zoom] sefadrin:
Hi.today I researched cwm recovery for s4 zoom different places,but I can't found.Can anyone help me for cwm?:crying:
[Samsung Galaxy S 4 Zoom] opdrago:
there is non for now, i couldn't find one either.
[Transformer TF300T Q&A, Help & Troubleshooting] soudy1994:
i just unlocked my bootloader couple of weeks ago and i installed a custom rom

if flashed the official firmware again will i be able to get the OTA official updates?
[Transformer TF300T Q&A, Help & Troubleshooting] sbdags:
Nope. You've forfeited that now.
[HTC Incredible S] szezso:
Szezso proudly presents

CyanVivo 10.2

The Incredible S is still alive, even if it's legacy!​

So, let's see, what everyone wants to know:​

fastboot flash boot boot.img

Download section:

​

And a proper GApps, you need to flash this too:​

​

Credits:​

- CyanogenMod

- legaCyMod Team

- Google

- hTC

- AMD​

Changelog:

- 08/25

- Initial release, first BETA version! :)

- 08/26

- Video Recording fixed

- Camera fixed

- Keyboard FC fixed

- Built-in Torch app fixed

- 08/26, Beta #3

- Fixed FFC

- Fixed button rotate

- Fixed releasetools

- 09/24

- Fixed SELinux

- Fixed Video Playback

- CM sync

- Removed Focal (merged)

- Kernel 3.0.96

- 09/30

- Kernel 3.0.97

- Fixed rotating buttons

- Some messing around in the Audio HAL source, but it won't fix the issue, I think

- CM sync

- 10/05

- Kernel 3.0.98

- Fixed WiFi

- CM sync

- Performace updates

- 10/08

- Kernel 3.0.99

- Ringtone bug fixed!!

- CM sync

- 12/02

- Android 4.3.1

- CM sync

- TESCO 3.1.2

- Ringtone fix included

- 09/15

- CM sync

- TESCO-Minimal 3.7.2 (same as Vivokat)

- Now using ION

- Adreno drivers from CAF's jb_vanilla branch

- Fixed Torch

- Fixed screen-off animation

- Fixed green tint in camera

- Fixed Root

Sigpics:

Thanks to achilles08

Thanks to l36320

Thanks to omareziz
[HTC Incredible S] szezso:
Stable #3 bugz:

Capacitive buttons brightness bug: button's brightness is no longer changed when changing screen brightness - it always stays at max. Perhaps it's a side-effect of CM introducing new feature - controlling time-out of button's light

Wi-fi on screen-off bug: when screen is turned off, wi-fi activity halts. I.e. if you download something through wi-fi and turn off display, then download will stop as well (actually it will continue through 3G, if available). Disregards setting about wi-fi mode with disabled screen. 3g continues to work with screen off without any issues. This bug was present in 10.1 as well and, perhaps, in 10.0 too.

Failure to wake up from deep sleep bug: not really traceable. Happens randomly. Phone fails to wake up from deep sleep sometimes. It may happen when it's charging or just when it's idling on the desk, still, the bug appears regularly every few weeks. Might be caused by some voltage tweaks in kernel.

Thanks [MENTION=4451231]TheQwertiest[/MENTION] for pointing these out! ;)​
[HTC Incredible S] deepu28792:
finally something new...i was waiting for this only..thnx szezso
[HTC Incredible S] szezso:
FCing keyboard fixed already. :)
[HTC Incredible S] szezso:
Camera fixed! :) (Pictures at least)
[HTC Incredible S] Eternalman:
Nice, Bro! Oh, is there any visual changes in a comparison with CM 10.1?
[HTC Incredible S] sabret00the:
Awesome. Thanks!
[HTC Incredible S] Eternalman:
Hey Bro! I just found some bugs for you :D

1- Volume buttons are not working.

2- None of the buttons except home button are working for me.

3- CM Updater starts force closing after running it.

4- USB debugging (ADB) doesn't seem to be working.

5- Terminal emulator is not working. It is, but the commands are mostly not working...

6- Superuser is not working. I flashed SuperSu

It is really smooth by now. Keep the good work Bro! And BTW, Sorry about the audio things :o;)

Well, here is the funny thing. After I installed JellyBeen Keyboard, the volume and other keys are responding. Actually after setting it as default keyboard...
[HTC Incredible S] arsh79221:
Awesome! Good job brother, you're genius :good:
[HTC Incredible S] And-rois:
Your work alive man now all like you ....

So you huge ....
[HTC Incredible S] szezso:
I only found one yet, the wallpaper choose screen changed:

No matter, you don't know something, what I know... :o The buttons not working issue is because of the keyboard. :) Fixed now. ;)
[HTC Incredible S] Eternalman:
SuperSU

Superuser wasn't working so I flashed SuperSU and this is what I've got from it:
[HTC Incredible S] Rah0ol:
Whoa !! a 4.3 ROM!! Thts really amazing :D

I am just waiting for Sense 5.0 Rom to clear out the bugs :D But This sure is a breakthrough..

As I was telling my friends, Incredible S gets even the latest updates thanks to Devs like You :D!!! :cowboy:
[HTC Incredible S] szezso:
Video recording fixed too. :)
[HTC Incredible S] poondog:
You're a superstar :)
[HTC Incredible S] szezso:
Update!​

Changelog:

- Fixed Camera (FFC still broken)

- Fixed video recording

- Fixed built-in Torch app

- Keyboard FC (and buttons) fixed too :)

Now broken:

- Button rotate (New one is building with this fixed)

- FFC (Maybe this too)

- Video playback (I'm sure this will be fixed in the recent building :))
[HTC Incredible S] 072665995:
Swweeeett lol. You're a couple hours ahead of me so when you post 8/26, I'm like, Wait what?? Cuz its still 8/25 local time for me :p

Anyways Great job Szeszo. Gonna download now and try and test a bit.
[HTC Incredible S] wert741258:
That's very Incredible...:good:
[HTC Incredible S] @di:
I think your incS must be thinking, when is this guy going to give up, I had a taste of gingerbread, icecream sandwich, jellybeans..... my god i had so many deserts over a period of time...... this phone has great capability to Eat when we have chefs like Szezso who make every ROM dish so delicious that every desert is digestable with no constipation!!!!!!!!

Whats next in the store another desert "KLP"? :p
[HTC Incredible S] deepu28792:
+1
[HTC Incredible S] szezso:
Okay, now building again, I really, really hope that the issue was with the include files... If it'll boot, the Vdec issue will be fixed. :)
[HTC Incredible S] odinko:
Crossed fingers
[HTC Incredible S] RmatriX1218:
Really eager....have you fixed issue?
[HTC Incredible S] szezso:
Okay guys, I have no time to test, cause I need to go to school, will be here with the (hopefully good) news in 9 hours. :)
[HTC Incredible S] achilles08:
will wait eagerly
[HTC Incredible S] Gizmo648:
Wow Battery life is just amazing
[HTC Incredible S] RmatriX1218:
Sorry guys, but bit confused. [MENTION=4622338]szezso[/MENTION] is struggling to getting it boot.

Other side users are reporting performance.

Is [MENTION=4622338]szezso[/MENTION] is trying some new build apart from one in OP?
[HTC Incredible S] Gizmo648:
His updated version is not booting atm, version in OP should work fine
[HTC Incredible S] szezso:
Still doesn't boot, and I have no more ideas... :(
[HTC Incredible S] Splux:
Is it possible for you to revert like 1 or 2 major changes at a time?

In that case it'd be possible to find which change it's that made it screw up and you'd leave us with at least a trace add to where we should look to make it bootable :)
[HTC Incredible S] Troj80:
I try build rom using your repo. Possibly log ADB will be useful to you...

I/Netd (13104): Netd 1.0 starting

D/MDnsDS (13104): MDnsSdListener::Hander starting up

D/MDnsDS (13104): MDnsSdListener starting to monitor

D/MDnsDS (13104): Going to poll with pollCount 1

I/auditd (13309): Starting up

E/auditd (13309): Failed on audit_set_pid with error: Protocol not supported

I/auditd (13309): Exiting

I/Netd (13315): Netd 1.0 starting

D/MDnsDS (13315): MDnsSdListener::Hander starting up

D/MDnsDS (13315): MDnsSdListener starting to monitor

D/MDnsDS (13315): Going to poll with pollCount 1

I/auditd (13520): Starting up

E/auditd (13520): Failed on audit_set_pid with error: Protocol not supported

I/auditd (13520): Exiting

Cyclic error :(
[HTC Incredible S] szezso:
Thanks for the log! Actually, I can try out something to fix in the kernel, to add SELinux support.... Cause these errors because of the lack of SELinux support. :)
[HTC Incredible S] szezso:
Okay, support added, here is a kernel updater: http://d-h.st/ZuV

I have no time at the moment, but that would be great if you could try it out. :) [MENTION=4702054]Troj80[/MENTION] Flash the ROM, then flash the kernel, and we'll see...
[HTC Incredible S] batculp:
I've flashed the ROM, then the kernel. What should I see? SeLinux status is shown permissive. Video playback still doesn't work. Audio bug with incoming call is here too. Maybe you can upload fixed rom which go in bootloop and we can change some files from beta3 to fix. I like to test my phone and could do it
[HTC Incredible S] szezso:
Could you give me a screenshot of that SELinux status? :)
[HTC Incredible S] batculp:
Here you are :
[HTC Incredible S] szezso:
Okay, netd issue, will try something.

Sent from my HTC Sensation Z710e using Android 4.1.1 + Sense 4+ and xda app-developers app
[HTC Incredible S] szezso:
Great, we got the SELinux working. :)
[HTC Incredible S] poondog:
Nice sensation bro :)
[HTC Incredible S] Eternalman:
Awesome!
[HTC Incredible S] RmatriX1218:
So where are we?

Eagerly waiting to get this as stable ROM, probably will be last one on my IncS. :(
[HTC Incredible S] szezso:
Mate, could you make a logcat of the Beta #3? I wanna see what MDnsDS is doing there... :)
[HTC Incredible S] Troj80:
Okay, new full ADB log.
[HTC Incredible S] Eternalman:
@Szezso, Could you make an AOKP ROM?
[HTC Incredible S] szezso:
Okay mate, thanks, I'll try my best...
[HTC Incredible S] szezso:
I can't promise anything, I have many studies, and I'm porting Sense 5 to Sensation, and also working on the kernel. I'll try, but at first, I wanna get the CM10.2 booting again...
[HTC Incredible S] zhong00123:
I used your media-legacy source and built a cm10.1 last night , and I can confirm that video playback does not work in cm10.1 now :(
[HTC Incredible S] szezso:
Can you give me a logcat?
[HTC Incredible S] Troj80:
I think that it is not in the kernel, for example if I take the bin and library out of beta 3 and replace the ones that I have compiled rom, I get downloadable rom :). Perhaps the case in the source CM :eek:? Although I could be wrong ... In any case, mate good luck! ;)
[HTC Incredible S] szezso:
Yeah, the issue must be in the source. :)
[HTC Incredible S] Troj80:
If I understand correctly, the files from your repository /szezso/proprietary_vendor_vivo/tree/cm-10.2/proprietary are pre-compiled and just copied to the rom in the building?
[HTC Incredible S] Eternalman:
Well, thanks for the reply! Take your time, Bro!
[HTC Incredible S] szezso:
Yep!
[HTC Incredible S] Troj80:
Then it turns out it is because of them that we get bootloop. I'm try to copy them into a working beta 3 rom .. The result - bootloop...:eek: Heh, so it is, my compiled rom now booting and work :cool:
[HTC Incredible S] szezso:
Really? Oh my God, then my vendor is wrong! :eek: Thanks for pointing this out, I still need to study a bit, but I'll get out the Vivo from its box, and I'll try it out! :)
[HTC Incredible S] Troj80:
Yes, yes, yes mate :). I'm sucessful boot.:laugh:

Say me please, in sources, where can in TARGET_CPU_VARIANT=scorpion else cortex-a8?
[HTC Incredible S] Eternalman:
Really? What about the audio bug and VDec? Are they fixed?
[HTC Incredible S] szezso:
Tell me, tell me, tell me, what was wrong?! :)

Leave it as scorpion, it works. :) Please tell me, which thing is wrong, so I can fix the vendor. :)
[HTC Incredible S] Troj80:
Unfortunately there is no, i'm used *.so from beta 3 rom.

Can not say exactly, I just did the opposite of what I wrote above you but I guess it's about what some of the libraries most likely culprit libsurfaceflinger_client.so, while it is possible that anothers...

No, no, i'm try build using another repo, in this repo default TARGET_CPU_VARIANT=cortex-a8, we probably will not do...
[HTC Incredible S] szezso:
Okay, then I'm building again... I don't know, why did I left it there...:confused:
[HTC Incredible S] szezso:
Okay, the build is going now, this update HAS TO FIX the Vdec issue!
[HTC Incredible S] Troj80:
[MENTION=4622338]szezso[/MENTION]

So where is set to TARGET_CPU_VARIANT?
[HTC Incredible S] szezso:
Where is to set? :) In the Boardconfig.mk, or Boardconfigcommon.mk.
[HTC Incredible S] Troj80:
[MENTION=4622338]szezso[/MENTION]

Thanks mate. I will try.

f**k this is not libsurfaceflinger_client.so...
[HTC Incredible S] ryanmeray:
I will be so happy if this results in a working and bug-free Vivo 10.2. XD
[HTC Incredible S] RmatriX1218:
Not only you but many will be happy..:o

All eyes are on this development thread...as this will revive their phone for say for another six months at least:good:

I am checking this thread four to five times a day just to get news of working rom. Never been so eager as like this time.:o
[HTC Incredible S] szezso:
Not that makes the issue? I haven't got the Vivo anymore, so, I can't test. :(
[HTC Incredible S] funCrash93:
[MENTION=4622338]szezso[/MENTION], believe in us, people who have the will to test your dev-ing, we are here.;)

just give us smth to test for you and we will with pleasure.

so don't ya worry about testing.;)
[HTC Incredible S] Troj80:
Not that makes the issue :(... I have personally the problem in libraries of camera, but I do not understand why they cause bootloop.
[HTC Incredible S] uprockin:
It is like that, I am looking at myself :)
[HTC Incredible S] szezso:
Exciting, anyway, I built one, with source-compiled libsurfaceflinger_client.so, will upload it after I got home. :)
[HTC Incredible S] Eternalman:
You know if it boots or ... ? You need any testing?
[HTC Incredible S] szezso:
I need to upload it, I haven't got the IncS, so... :)
[HTC Incredible S] Eternalman:
Alright then. I'll be waiting for the new release...!:fingers-crossed:
[HTC Incredible S] iSeanzh:
I never check Xda forum this thread this frequent, I feel excited whenever I see a notification that [MENTION=1132633]szeszo[/MENTION] has a new post.. I will wait and try one last rom then will change to either Nexus 4 or 5 (if 5 can be released this year)
[HTC Incredible S] szezso:
My latest testbuild, I have no idea does it work or not: d-h.st/V1R
[HTC Incredible S] Eternalman:
I'm downloading it. Will give you the review!
[HTC Incredible S] ryanmeray:
The suspense is killing me! I feel like I'm in a movie waiting for the loading screen.
[HTC Incredible S] 072665995:
So umm, how long should I wait for it to boot up? I've been sitting for like 10-15 minutes and I still have a bootanimation...

Should I wait any longer? Or what...
[HTC Incredible S] Splux:
I think you should try to get a logcat...
[HTC Incredible S] szezso:
Great, it still doesn't boot... :mad: [MENTION=4702054]Troj80[/MENTION], did you find out, what makes the bootloop problem from my vendor?
[HTC Incredible S] batculp:
I know what lib files causes bootloop. They are libcamera_client.so and libcameraservice.so. I compare all files in new ROM and beta3, then had changed lib files from new ROM to beta3... Finally I found out that only this two files causing bootloop. Then I copied this files from beta3 to new ROM, and it booted normally. But, unfortunally, audio bug and video playback bug still exist. Problem not in them. Later I wll try to change libs from cm10.1, but it's need a lot of time and not guarantee that it helps.

And forgot, Szezso, in knew ROM keyboard crushes, you may be forgot something, changing lib libjni_latinini.so from beta3 fixes it
[HTC Incredible S] Troj80:
bootloop problem libcamera_client.so and libcameraservice.so...

Replace only lib not fixes it. Maybe need replace apk. And

keyboard crashes maybe problem source CM... Need time for build latest CM source.
[HTC Incredible S] szezso:
Building... Thanks guys! I f*cked up my source, I don't know, why, but I finally know, what should I do, cause I remember... :)

Sent from my HTC Sensation with Sense 4+.
[HTC Incredible S] Troj80:
Good luck mate! Await! ;)