yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] duckredbeard:
I had abandoned my vivid after my battery went south. I was unlocked, rooted and S-On. I had installed a CWM recovery which prevented off state charging. Since the battery was dead, I could not charge the battery. I now carry a Galaxy S4.

I have since relocked the device and updated to 4.0.3. I intend to root this device and update to the latest recovery/bootloader/and this ROM but I'm a bit detached from what this device needs for such antics. I used the Superguide and a few other threads to do the relock and update but I still have questions. I can unlock no problem. Do I need S-off for this ROM? Do I need to update the bootloader?

You don't know your limits until you exceed them.
[HTC Vivid, Raider, Velocity] Jaxellis:
No. Use wcx's recovery please instead of CWM ... wipe everything. install everything. flash boot.img .. enjoy
[HTC Vivid, Raider, Velocity] duckredbeard:
So I need to "need to flash the boot.img in the rom.zip"...I think this is what I need to do: made a copy of the ROM and unzipped it...copied the "boot.img" and the original zipped ROM to the SD card, then flash them both?

Do you have a link to WCX's recovery?
[HTC Vivid, Raider, Velocity] pitpit24:
You better make sure you really understand how to flash boot.img before trying to flash anything else.
[HTC Vivid, Raider, Velocity] duckredbeard:
Good advice and thanks for looking out for me. Is there a walkthrough? Is it a fastboot flash or flashed in recovery?
[HTC Vivid, Raider, Velocity] rignfool:
Fastboot flash for the boot.img... And recovery flash for the ROM...

If you aren't relying on the phone day to day... Do the s-off process and brag about how easy it is...
[HTC Vivid, Raider, Velocity] Wolfhawke:
Even if you are relying on the phone, go ahead and do S-OFF...it's worth the time...
[HTC Vivid, Raider, Velocity] NWinfuse:
If you use Flash image GUI from the play store s-off really isn't all that important since you can flash the boot.img without using fastboot
[HTC Vivid, Raider, Velocity] rignfool:
Or from the thread in vivid apps and themes... You can get it free
[HTC Vivid, Raider, Velocity] NWinfuse:
True, you can get it free but I decided to buy just to support the dev :D
[HTC Vivid, Raider, Velocity] bkman08:
Anyone else know this update happened? o.o
[HTC Vivid, Raider, Velocity] calikevin:
Did the update ever happen or was it just planned? I only ask because the date is still 11-xx-13 and I was unaware of the update until now... And there's a couple things striked out in the changelog

Edit- rom date is 9/12
[HTC Vivid, Raider, Velocity] Jaxellis:
Itll come out sometime this month hopefully. Having trouble compiling.
[HTC Vivid, Raider, Velocity] alex4659:
if im s-on, do i need to flash the boot.img file via fastboot?

thanks,

Alex
[HTC Vivid, Raider, Velocity] Jaxellis:
I may just take a guess and say you didnt read it. But there ya go​
[HTC Vivid, Raider, Velocity] pitpit24:
Just try it without flashing boot.img, then you'll know what it makes and why you must always flash it with this device. Haha.
[HTC Vivid, Raider, Velocity] alex4659:
face palm. i must have over looked it.

thanks. my bad.
[HTC Vivid, Raider, Velocity] Jaxellis:
Guys im not sure if i can compile pac 4.3. For some reason it just really doesnt want to compile and everytime i fix one error 10 more errors pop up. Buuuuut I'm not forgetting about you guys. Pac 4.4 is hopefully on its way
[HTC Vivid, Raider, Velocity] NWinfuse:
Too bad 4.3 isn't coming together, thanks for trying
[Nexus 7 (2013) General] Fussolia:
This comes up every time I try to use Netflix. I bought this tablet yesterday morning and I haven't been able to use Netflix yet.

I've tried reinstalling it and clearing user data.

EDIT: I just got the JSS15Q update and Netflix now works!
[Nexus 7 (2013) General] gandda12:
Try signing off netflix and sign back in.
[Nexus 7 (2013) General] FrauPerchta:
Netflix worked for me first couple of days then quit and gave me errors. I ended up uninstalling Netflix after trying everything in the threat about the issue then installing it again and it has worked every since.
[Nexus 7 (2013) General] muyoso:
Netflix has been absolute garbage for me on the Nexus 7. I have to sign out and back in almost every time I launch the app for it to work correctly. I've gotten those errors before, and I've also had it sit at the loading screen for ten minutes doing nothing.
[Nexus 7 (2013) General] DroidScoop:
Try heading to (settings>apps>all apps>netflix> wipe data & cach ) let us know how it goes

Sent from my Moto X Infused GS3
[Nexus 7 (2013) General] unni_kmr:
I get this message at random. Sometimes, the app itself logs me out and prompts for user name/password after showing this message. Then it works.
[Nexus 7 (2013) General] DroidScoop:
If you can try and find the .apk file for a previous build. The current up to date file could have a bug.

Sent from my Moto X Infused GS3
[Nexus 7 (2013) General] Fussolia:
I was never able to sign in in the first place. I get this error on the splash screen.
[Nexus 7 (2013) General] Fussolia:
Thanks, but that didn't change anything.
[Nexus 7 (2013) General] Omar04:
Netflix have been on undergoing changes that's why sometimes issues arise but are temporary. They updated the app, to work with 4.3 squashed some bugs and now they are adding features to the service. Everything is working fine on my end, also due to this is not only the Android app same happened with the site on PC and on my PS3, but all is working now.

And please stop blaming the Nexus 7 "Flo" for every single issue when are the apps that have the issues.

Team SXTP
[Nexus 7 (2013) General] bosscar:
I am getting the same 15001 error in NetFlix... reinstalling, clearing cache, even factory reset did not help yet :(
[Nexus 7 (2013) General] bosscar:
Just realized after the OTA update: JSS15Q... Netflix started to work :) Now i can start chrome casting :laugh:
[Nexus 7 (2013) General] Fussolia:
Yup! Netflix finally works!
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] mutonic:
Hello,

In short my question is:

Is there a way to always get back its device into working state (even if Recovery Menu is corrupted).

by using ODIN menu for instance to reflash bootloader

Long version:

Through this topic I was willing to gather some knowledge on the different way to modify a Stock device (possibilities, risks, )

Everywhere we can see "Be carefull, your device could be damaged, do at own your risk" and on...but what is the real risk undertook behind that warning?

I start from an original device (Official stock rom, unrooted).

Before going further, here is the summary of some info on the different methods I could see:

-Official Samsung recovery menu accessible holding Vol. UP + Home + Power Button while starting device

-> a the way to flash OFFICIAL ROM directly on the device (without using a computer)

-Official Samsung ODIN menu interface accessible holding Vol. Down + Home + Power Button while starting device

-> a way to flash ANY ROM on the device but using software computer ODIN

-A Fastboot menu accessible holding Vol. Down + Vol. Up + Power Button while starting device

-> which I don't know exactly what it is doing

First step to get a modified device would be changing Official Recovery bootloader into Custom one in order to patch unofficial rom later on.

For doing that, ODIN menu (which has the ability to flash NON OFFICIAL image) is used to replace the bootlader with a custom one (e.g. CWM: Clock Work Mod).

Once the new Custom Bootloader is present, it can freely flash ROM. (which should be without danger, as if a ROM is corrupted it can be flashed again with the Bootlader which is always present)

My guess is now, what happen if the bootloader is broken?

Let's say I want to try to run a linux distro on the device which required to modify bootlader to boot directly on Linux instead of Android.

As I would normally think, ODIN menu is still there to enable flashing back another Bootloader and get the device back to working? Is that right?

Regarding ODIN, does anyone know if this is the safe mode which cannot be altered and is always able to bring back the device to normal?

Thanks for giving me any insight on this subject, as I am eager to do some experiment with my device but would be sure not doing anything wrong.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] abhishekr700:
Hello everyone

i want to know if there is a way to use me android device as a wifi adapter for my pc

i mean i connect my mobile to pc via usb and use my mobile as a wifi adapter for pc.......
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] =-=:
I hope this link can help you :)

BTW .... search before posting :victory:
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] abhishekr700:
i want to know how my pc can detect my android as a wifi adpter

i dont want to use internet

thers some other suff that i wanna do
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] PAPalinskie:
I think it is usb tether and a wifi antena itself. Try to plug your phone and go to settings-wireless connections-tethering-activate your usb tethering(if your phone have its settings and also drivers required). Then activate your wifi.

sent from my throne
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] crash.override:
You can use wifi tether or usb tether.

If you use usb teher, you must install usb driver to your computer first
[TouchPad Development] flintman:
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.

Right now the current source we are working on is Jellybean (Android 4.3).

Current version: 3.3.0p1

Current Items not working/Buggy

Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[TouchPad Development] flintman:
For all having issues with UMS and Windows try this

1. Go into Device manager. You will see "MTP USB Device" under portable devices.

2. Right Click it and select update driver software

3. Select Browse my computer for driver software.

4. Select Let me pick from a list of device drivers on my computer

5. Select USB Mass Storage Device then click next.
[TouchPad Development] DanFunky:
I'm happy to test, and will give feedback, just nervous without an MD5 as I've been burned with that several times.

I got 51FAF49CAAD109204B0368AAF59684DF.
[TouchPad Development] flintman:
MD5 51faf49caad109204b0368aaf59684df
[TouchPad Development] MerenQue:
With TWRP 2.6.0.0 I wiped TouchPad first than I flashed your ROM with Gapps for Android 4.3: http://wiki.rootzwiki.com/Google_Apps#20130813

1.) In my case "Turning Wifi on" doesn' t work.

2.) SOD (“sleep of death”): Screen goes off but I couldn't wake it up by pushing the power button.

3.) Reboots by itself.
[TouchPad Development] flintman:
Try to flash with out the gapps and see if it works i have tried both ways with no issue. Also if you can get a logcat that would be great
[TouchPad Development] DanFunky:
I have no problem with WiFi. multiple users works great so far, and can't be happier.

I did a full reset, wiped everything including SD card and copied it over under WebOS to be sure.

I'm on TWRP 2.3.3.0, and the only thing I've noticed is rebooting into anything like bootloader or recovery always defaults back into the menu with Evervolv selected, but you can always use the menu to select something else.

Love the new toolbox (although the multi-way UI takes some getting used to...trying to please everyone I assume) and updater...I just used it to install GApps which is FANTASTIC!!! Thanks for having core and full GApps.

Great so far, I'll kick the tires more today.
[TouchPad Development] MerenQue:
I didn't know that Gapps 4.3 is implemented in Evervolv. Now I've flashed it without the gapps and have no SOD and no Reboots anymore! But still "Turning Wi-Fi on..." - without success. :(

To make a LogCat for you I tried to install via USB "KernelTuner-4.4.7.apk" - everything fine so far - but I don't have a File Manager to install the apk. Sorry.
[TouchPad Development] flintman:
I just uploaded another test it's called test 2. Try that out. Also everyone if you could instead of test 1 try test 2 and tell me which one works for everyone.

Thanks.
[TouchPad Development] MerenQue:
Test 2

WiFi connected successfully! :good:

Big Thanks!
[TouchPad Development] flintman:
Glad that worked. Now just want to make sure everyone else is working
[TouchPad Development] smashtheguitar:
Playing around with Test 2 and its working amazingly well thus far. WiFi works, but can't get Bluetooth to start. Otherwise its very smooth. Great work!
[TouchPad Development] flintman:
Bt is still broken. If wifi is good I want to fix thr issues with the mic
[TouchPad Development] DanFunky:
Not sure what's changed, but a dirty flash seems the same after letting it settle a couple...still no Wi-Fi issues here.
[TouchPad Development] vinukondamahesh:
WiFi connected successfully
[TouchPad Development] flintman:
Test 3 is up. This has some audio changes along with a working mic. Wifi is still the same as test 2. If you download a camera launcher from the Play store you can use the camera and camcorder. Will look into why that doesn't display.
[TouchPad Development] vinukondamahesh:
iam not able to open play store,gmail after test 3 update
[TouchPad Development] flintman:
Did u dirty flash? Also can you provide a logcat?
[TouchPad Development] vinukondamahesh:
before installing test 2 i did dirty flash,but nw i updates with current rom and i dont knw how to create logcat
[TouchPad Development] flintman:
http://xdaforums.com/showthread.php?t=1726238

Here is a pretty good tutoral. Also backup and wipe data and cache and see if that fixes your problem. One other thing is did you reinstall gapps when you installed evervolv again as evervolv formats the system partion and then installs so it will wipe gapps
[TouchPad Development] garux:
Android.process.media

After keying my password, I get the following message:

Unfortunately, the process android.process.media has stopped.

I did a clean install.
[TouchPad Development] detdett:
Which gapps package did you flash
[TouchPad Development] garux:
I tried 2 different times.

gapps.jb-20130813-signed.zip, also tried gapps.jb-lite.20130813-signed.zip both came from a clean install.

To resolve the problem, I did the following:

Settings/Applications/All/Download Manager and Clear Data/Cache

Settings/Applications/All/Google Bookmarks Sync and Clear Data/Cache

Settings/Applications/All/Google Calendar Sync and Clear Data/Cache

Settings/Applications/All/Google Contacts Sync and Clear Data/Cache

Once done and re-booted, the problem went away.
[TouchPad Development] garux:
It appears my previous message on the fix was a band-aid. I think i found the real problem, but I need more time testing. Just to let you know, it's not an Evervolv or gapps problem.

Will report back tomorrow.

Sorry for the inconvenience.
[TouchPad Development] Y314K:
Do u guyz know if the latest CM10.2 datamedia recovery aka "recovery-clockwork-datamedia-6.0.3.6-20130926-tenderloin" by Milaq is compatible with this build ??? Would prefer to just have one recovery that is compatible with both 4.3 builds (Evervolv & CM10.2) & maybe even with Schizoid Final installed for easy switching...
[TouchPad Development] garux:
I know the Evervolv nightlies location is: http://evervolv.com/devices/tenderloin

I can't figure out how to setup GooManager to look for the Evervolv nightlie updates.

Could somene tell me what I'm doing wrong.
[TouchPad Development] jerryatherton:


---------- Post added at 10:23 PM ---------- Previous post was at 10:22 PM ----------

Use the EV updater in settings.
[TouchPad Development] garux:
My problem was in the setup of Antutu Cpu Master, I had boot startup checked on all options. Once removed, my problem was resolved.
[TouchPad Development] RolandDeschain79:
SU issues with dirty flash

Hi Flintman,

I was trying out a dirty flash with the latest Evervolv build over CM9(skitzoidCM10) and noticed that I kept getting asked about SU permissions and this seemed to lead to a random reboot. So I tried to enter the SU app and give everything permission but got greeted with a msg saying the SU binary had to be updated, screenshot below. I tried to update it the normal way and that failed. I tried allowing it to happen via recovery and that caused the Rom not to boot. I wiped caches and reflashed to get back to my home screen. I've tried to get the last kmsg but it doesn't appear to be populated. Is there another way in which I might retrieve this for you? I was wondering if some sort of issue with permission and dirty flashing was causes problems since I didn't seem to get reboots when I fresh installed. I'll try doing a fresh install and see what happens when I open the SU app. Thank again for this awesome 4.3 Rom

http://paste.evervolv.com/view/e36ad78c

Update: I actually think I may have dirty flashed over Shumashs CM10 build, oops sry I flash a lot. After doing a fresh install I don't even see the super users permission app and think this may have been left over from my previous Rom. I wonder if there is some problem with SU permissions after dirty flashing causing reboot issues. I will need to go back to CM9 flash over that and see what happens.
[TouchPad Development] flintman:
Dirty flashing from cm to ever never works
[TouchPad Development] JeremyNT:
Worked fine for me going from cm9 to latest nightly at the time. Though obviously YMMV.
[TouchPad Development] RolandDeschain79:
Thanks for the response Flintman. I will make a note about that, its an important point. You may wish to note it in your OP too. I would put something like. A fresh install is required when using Evervolv AOKP roms. Dirty flashing an AOKP rom over a CM rom may cause reboot issues or errors.

If Flintman says it a problem then, its probably best to avoid dirty flashing AOKP roms over CM roms. This is might be the cause of the random reboots people have been reporting since my fresh install isn't plagued by such problems.

Edit: I just realized I didn't mention this in my video and will need to make notes about that there too, sorry Flintman
[TouchPad Development] flintman:
Not a problem ill update it in the first post. Thanks for the great videos
[TouchPad Development] RolandDeschain79:
Ingenious Developer and Awesome Rom!

Thank you for the incredible Roms and your brilliant development work, i'm excited to see BT appear in your Roms once again:D

I added a little note about doing a fresh install, sorry I didn't think of doing this sooner.

Note(Important): This is an Android Open Source Project (AOSP) rom not a CyanogenMod (CM) rom. Dirty flashing an AOSP rom over a CM rom can causes errors and rebooting issues. Always do a clean install when moving from CM to AOSP and vise versa.
[TouchPad Development] garux:
Hi Roland, are you talking about the 'Bluetooth Share' app that appears in the laundry list of apps in settings?

Does this mean a startng point to soon seeing Bluetooth working?
[TouchPad Development] Y314K:
Great rom flintman... Thanks for the fast work on 4.3... Was able to try both Evervolv 4.3 & CM 10.2 over the weekend... And as expected... The first one out the gate evervolv runs just a tad smoother then CM 10.2... Although both are fast & stable roms...

I did have one ?... Is there a setting I missed on Evervolv where one can resize app widgets into a smaller area like I can on CM 10.2 or is this an app widget problem or a feature that is missing on Evervolv... When I try to change the size of the digital clock widget to a smaller area... It keeps springing back to it's original size...
[TouchPad Development] jerryatherton:
I have problems with clock widgets also, some are re-sizable and some aren't.
[TouchPad Development] waynekirby:
That's just the way they are in AOSP, blame Google :D
[TouchPad Development] orangecream:
Just want to pop in and say thanks to the devs for breathing new life into my TP. Just flashed from CM9, I'm really loving this build.
[TouchPad Development] Y314K:
After moving some of the apps from CM10.2 to Evervolv 4.3... I was able to confirm that the major reason for the difference between how both stock roms handle resizing is not because of AOSP.... But it's as simple as the launcher both builds come with...

Evervolv comes with Launcher2.apk & CM10.2 comes with Trebuchet.apk... Normal stuff... So once I added/sideloaded Trebuchet.apk to Evervolv I was able to get the smoothness of Evervolv with the same type of resizing as CM 10.2... On Trebuchet u are able to put shortcuts on the left & right edges too in landscape mode...

I ended up moving/sideloaded the following apps...

Apollo.apk

CMFileManager.apk

LockClock.apk

Trebuchet.apk

Now I have the best of both worlds...

Trying to find out if there are any difference between both DeskClock.apk files... Different sizes...
[TouchPad Development] waynekirby:
Launcher2 is part of AOSP.
[TouchPad Development] Y314K:
Ahh.. Good to know... Edited prior post...
[TouchPad Development] tft:
is it possible to change the appearance of clock when docked?
[TouchPad Development] flintman:
Tomorrow the reboot to recover is fixed and todays nightly fixes the delay coming out of sleep. A dirty flash should be OK but if you have any issue perform a clean flash.
[TouchPad Development] RolandDeschain79:
Good news everybody!

Great news Flintman thank you:good: I will test it out, I always forget booting to recovery doesn't work and tend to have to reboot it twice:o
[TouchPad Development] Sepharite:
Just updated to the latest nightly. Runs amazingly, and the battery seems great compared to my 1.5 year old Cyanogenmod ROM.

However I can't seem to install any new apps. I'm getting a 500 error, download failed. Any idea what I can do?
[TouchPad Development] jaamoke:
I think the problem was with the Google Play Store. I tried to access it with two different devices and received the 500 error on both.
[TouchPad Development] Y314K:
Yeap... Google Play store experiencing strange install/update errors [Update: it's working again]

Should be back to normal now...

Update: Like FlintMan stated... The 10/09/2013 nightly fixes the reboot to recovery prob... Tried it a few times & it worked perfectly each time... It bypassed moboot to go into recovery... Evervolv just gets better & better... Thanks FlintMan.... (Tested on the mediadata recovery... Working on switching to the regular CWM recovery right now...)
[TouchPad Development] garux:
YES! This most certainly is working.

Thanks Flintman for all your hard work maintaining this rom.
[TouchPad Development] agent00f:
No tabletui? How do people even use a 10" tablet with the phone interface? :)
[TouchPad Development] Y314K:
Guess u've been hiding under a rock for the last 2-3 years.... You can even do WiFi calling using some apps & Google Voice if u wish to...

HP Touchpad Evervolv Android 4.3 Overview!

Thanks to XDA-Dev's & RootzWiki... Best $99 tablet ever... Actually paid $150 for mine.. But that was because it came with the TouchStone & HP case... Brand new.. :good:
[TouchPad Development] agent00f:
I have 2 of these. 1 is on the jcsullins 4/13 build and the other 8/8 experimental with tabletUI patch. Want to try 4.3, but the problem with phone UI is that it not only takes up more space (most of it blank) the buttons in the middle require moving hands from the sides to hit, esp annoying for back. Is it hard to do tabletui or something? Seems like natural thing to fix if dev is putting any time into this.
[TouchPad Development] Y314K:
Right.. But compare to the pre-ICS... Even better now with JB... There should be some improvements... Major one's once it goes to 5.0 ... Guess portrait mode is u'r friend till then... I don't have much prob on landscape as is.. But they can always improve things...

Have u tried any of the dozen launchers out there....??