yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] chrismast:
That shouldn't be a problem at least if Google follows their announcement to optimize 4.3 for lower end devices.
[Galaxy S III Q&A, Help & Troubleshooting] Striatum_bdr:
Many people are running 4.3.1 in custom Rom, your remark is pointless.
[Galaxy S III Q&A, Help & Troubleshooting] sriram231092:
that is just my assumption. not decision. chill out.
[Galaxy S III Q&A, Help & Troubleshooting] chrismast:
Maybe his assumption is not totally pointless considering that current 4.3.1 are all aops (?), hence do not include TW which I assume will add additional memory load?!

But anyway no use to speculate, wait and see :)
[Galaxy S III Q&A, Help & Troubleshooting] Striatum_bdr:
Tw is a launcher, that's not the problem.

The only problem is marketing. Samsung want to promote newly cutting edge devices, and counting on the ignorance of 90% of its users, they try to invite a maximum of people to buy a new device to have new features, which are for a good part of them only software evolutions.

So after a 'security delay' to sell for example 40 million s4 plus the recent note 3 they eventually consider the older users..

With all their IT engineers they could have brought us 4.2 in a couple a weeks and same for 4.3.

Programmed obsolescence.
[Galaxy S III Q&A, Help & Troubleshooting] Mord0rr:
Unfortunately i im obliged to concord....:rolleyes:

According to 4.3 tread, maybe this week we have some news to S3...:p
[T-Mobile Samsung Galaxy Note II] cellrama:
I just picked up a Samsung Galaxy Note 2 (model: SGH-T889V) from my local WIND Mobile carrier in Canada as a backup device. To my knowledge, this is the same variant which is used by T-Mobile. I'm told the device hardware supports LTE but since WIND Mobile is not a premium carrier, Samsung has crippled this feature.

I have a Note 3 and after unlocking the device, I was able to use chainfire's method for ROOTING the device, installing TWRP recovery and then flashing with the Telus Mobility ROM (as all Canadian Note 3 devices are the same variant: SM-N900W8).

My concern is I am new to ROOTING/FLASHING and have searched the forums but am looking for concrete advice so I do not end up bricking my device. I am currently running Android 4.1.2 (stock from WIND at day of purchase) and when I go into the regional carrier settings, I do not see the regional code for Telus (TLS). I did see this on my Note 3 but I did not look until after unlocking and rooting so maybe it will not display until the proper ROM is loaded.

My questions are:

1) Can I use the same version of ODIN I have downloaded when ROOTING/FLASHING my Note 3?

2) Can I flash the same version of TWRP I did for my Note 3 or is TWRP device dependent? If I need a new version, could someone post a link for my model: SGH-T889V?

3) Can I flash the Telus ROM for their Note 2 variant (like I did my Note 3) or will this brick my device? If not, what ROM can I flash so I have LTE capability?

With my Note 3, it was straight forward! All I did was ROOT, FLASH TWRP recovery, install the Telus SM-N900W8 ROM, enable the regional setting for TLS and voila, I had LTE. I'm going to assume it's a little more difficult with the Note 2 but answering my questions and the guidance you provide would be much appreciated and help in my process. Thanks!
[Upgrading, Modifying and Unlocking] khalil_02:
Can anyone help me his to root lava iris 455 so that I can upgrade to android 4.3

Thanks much.
[Upgrading, Modifying and Unlocking] ummarrkhan:
rooting doesnt mean u can upgrade but u can try custom rom

here is how to root this http://xdaforums.com/showthread.php?t=2484554
[Upgrading, Modifying and Unlocking] nileshlchandak:
Increase RAM in Lava 455

Hi,

Please let me know how can i incraese the RAM in my Lava 455. At any given point of time free ram is around 100 mb which makes my mobile slow.

I have been looking for a solution since many days but no success.

Please help!!!!

Thanks

'Nilesh
[Android Software Development] (•.•):
Hello there

I'm about to strip my system of any useless (for me) function and/or app and restrict every possible spying activity.

I messed around with the system and deactived alot of bulk and spam. I also restricted all the stupid triggers with autostarts.

Don't know If anyone saw all the things going on behind the surface, using all the following things to analyse:

I'm using several apps to do so. Xprivacy, Android Firewall, Autostarts, Root Cleaner, Android Tuner, Root Uninstaller, LBE-Security Master and Root Explorer.

So my question to someone with experience is:

What exactly does the google play and also the google framework needs to work properly ?

Would be nice to know that.

cya
[Android Software Development] (•.•):
seems to be a big secret... ? I think, there are several commands in this play store like, if this app or this function does not get X, return "no connection", even if it got its connection...

no one knows ?

I think it is important to know...
[Verizon Samsung Galaxy S 4] lynyrd65:
New ideas are always appreciated. Thank you for your efforts!
[Verizon Samsung Galaxy S 4] Naddict:
There are two places to discuss this ...and remember, if you ever try any of this stuff, you do so at your own risk....

see http://xdaforums.com/showthread.php?t=2500826

or

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

or possibly here http://xdaforums.com/showthread.php?t=2428226
[General Accessories] dirkde:
Hello,

can someone tell me the layout of the 22 Pin connecor ? I have to build a new connector for my own.

Thanks

Dirk
[Samsung Epic 4G Touch] CSquare43:
I got an Virgin Mobile Galaxy S2 from a friend who was using it awhile ago but stopped because of some errors that he had with it (he doesn't remember what happened). He only had it @ 2 months before it broke, so it was basically brand new...

I'm hoping that IF it can be saved, that you guys can help me fix it.

When I start the phone, I get the Samsung Galaxy S2 GT-I190 screen. It then goes into recovery mode. Here is what that screen reads (underneath the recovery screen options):

--------------------------------------------------------

Deleting Cryption Meta Data

-- Copying Media Files...

Successfully copied media files.

# MANUAL MODE #

-- Updating application...

E:install_application_for_customer:Can't unmount/preload

copy application failed.

-- appling Multi-CSC...

Successfully applied multi-CSC.

--------------------------------------------------

If I try to wipe data (or any of the recovery options), it does nothing. I can move up/down using the volume rocker, but using the power button does nothing. The only soft button that does anything is the magnifying glass which brings up a screen with the android robot and an orange exclamation point inside a triangle.

SO....... :)

Is there a way to fix this?? If so how can I fix it? If I can't fix it, is it something that a shop could repair??

Thanks for all help. Much appreciated.
[T-Mobile Samsung Galaxy Note II] newky_nuke:
hey, i don't know if you all saw the emoji on Note 3 yet but the emojis are in color on it they are no longer black and white. do anybody know how to get color emojis on our Note 2??
[Galaxy S II Android Development] thereald:
Custom Bootanimations by TheRealD aka TheRealMofu

Feedback is always appreciated, please see which bootanimations are already planned before asking for a specific one, thanks

Greets

TheRealD aka TheRealMofu :p

Planned Bootanimations:

Releasing my 3D Final animations in diffrent resolurtions to serve more devices here on XDA and then releasing in diffrent colours

---> All files now on Dev-Host online, the link to my Dev-Host folder is at end of the OP !!! <---

---> All files also can now be downloaded by pressing "Download on Dev-Host" behind each animations name !!! <---

Android 3D Final: Download on Dev-Host

Android KitKat 3D Final: Download on Dev-Host

AOKP 3D Final: Download on Dev-Host

Beanstalk 3D Final: Download on Dev-Host

Carbon 3D Final: Download on Dev-Host

CyanFox 3D Final: Download on Dev-Host

CyanogenMod 3D Final: Download on Dev-Host

OmniROM 3D Final: Download on Dev-Host

Pac-Man 3D Final: Download on Dev-Host

PoundRom 3D Final: Download on Dev-Host

ReVolt 3D Final: Download on Dev-Host

RootBox 3D Final: Download on Dev-Host

SlimBean 3D Final: Download on Dev-Host

SlimSaber 3D Final: Download on Dev-Host

SlimSaber-@-Dorimanx Blue: Download on Dev-Host

SlimSaber-@-Dorimanx Green: Download on Dev-Host

SlimSaber-@-Dorimanx Red: Download on Dev-Host

SlimSaber-@-Dorimanx White: Download on Dev-Host

Pac-Man-@-Dorimanx Blue: Download on Dev-Host

Pac-Man-@-Dorimanx Green: Download on Dev-Host

Pac-Man-@-Dorimanx Red: Download on Dev-Host

Pac-Man-@-Dorimanx White: Download on Dev-Host

Carbon-@-Dorimanx Blue: Download on Dev-Host

Carbon-@-Dorimanx Green: Download on Dev-Host

Carbon-@-Dorimanx Red: Download on Dev-Host

Carbon-@-Dorimanx White: Download on Dev-Host

ReVolt-@-Dorimanx Blue: Download on Dev-Host

ReVolt-@-Dorimanx Green: Download on Dev-Host

ReVolt-@-Dorimanx Red: Download on Dev-Host

ReVolt-@-Dorimanx White: Download on Dev-Host

Carbon-@-NoKernel Blue: Download on Dev-Host

Carbon-@-Apolo Blue: Download on Dev-Host

PacMan-@-NoKernel Blue: Download on Dev-Host

PacMan-@-Apolo Blue: Download on Dev-Host

If I forgot someone to credit, be so kind and tell me, I will change it immediately ;)

Special Credits goes to:

[MENTION=4592271]ahmedelhofy[/MENTION] (for getting my newbie skills up in Cinema 4D)

[MENTION=4526073]Christiancs1969[/MENTION] (for supporting me in an awesome way)

Credits goes to:

Android

CyanogenMod Team

HardCorePawn

Fusionjack

Kroz

bluefa1con

CarbonDev

bajee11

Wiggierip

Dorimanx

Pedestre

PartimusPrime

johnhany97

Cyberboob

OmniROM Team

MNT_ & CyanFox Team

scott.hart.bti & Beanstalk Team

AOKP Team

Download on Dev-Host: ---> HERE <---
[Galaxy S II Android Development] ammarsg:
good thank you and you can also do for general roms not only slim rom ;)
[Galaxy S II Android Development] thereald:
Your welcome, for sure i could do it for other roms too, in your case i think it's pacman right ? ^^

But i need to clarify first if i get the permission from the pacman guru to use the logo, than i will do that :D
[Galaxy S II Android Development] farisyi1:
Carbon Rom please :D
[Galaxy S II Android Development] thereald:
You get the same answer, i'll check for the logo permission and get back to you that weekend :o
[Galaxy S II Android Development] farisyi1:
thank you.. i like if you add carbon rom + dorimanx kernel .gif :highfive:
[Galaxy S II Android Development] ammarsg:
thanks man .....but i mean general bootanimation which can be used for all roms not specific to one rom .....or you can learn me how to do this by my self :D .....i search here and get some idea but not work with me sooo i will try more and more
[Galaxy S II Android Development] r4svob:
Nice

Graphically very nice! And as farisyi1 said, Carbon + DorimanX would be really great :)
[Galaxy S II Android Development] thereald:
Sure i can do that as well, but it wouldn't make sense because the general animation itself without Rom & kernel logo is included in the normal cm10.2 Rom you can extract it and you will find it in the folder system/media :P

Will come that weekend as far as i get the permission for the logo...
[Galaxy S II Android Development] ammarsg:
[MENTION=1675953]thereald[/MENTION] i know cm bootanimation and extract it but i get other action bootanimation from all roms and replace it in every flash of the rom .....thanks and we wait for pac and carbon and maybe revolt rom also .....:good:
[Galaxy S II Android Development] j1gga84:
I tried to flash boot animation via CWM but it was not applied. When I put the file to system/media it works.

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] thereald:
OK thanks for your feedback, than i did something wrong with the installable zip, was my 1st try, sorry for that guys, I will fix it till tomorrow

Edit:
[MENTION=4699854]j1gga84[/MENTION] It's fixed now and I uploaded a new version :)
[Galaxy S II Android Development] luvmyXray:
thANKS

really nice.., thanks for sharing this awesome boootanimation
[Galaxy S II Android Development] zkibz:
Keep up the gooodwork sir.
[Galaxy S II Android Development] thereald:
A small update from my side, I recieved the permission today for the pacman Logo, for the carbon logo i'm still wait for permission so please stay patient and if you habe anymore suggestion for other roms, just tell me

Sent from my GT-I9100 with Tapatalk
[Galaxy S II Android Development] dorimanx:
Well done :)

I really like the Anim, using it now, and will carry it to next roms.

Very good graphic skills. :good:
[Galaxy S II Android Development] Verna KDM:
Can you do it for the cyanogenmod?
[Galaxy S II Android Development] thereald:
hmm i'm a bit confused now mate, because the animation is the one from cyanogenmod, the original one just doesn't has the logos on top and on the buttom, or would you like to see one with cyanogenmod writing at the top, in the middle the animation and at the buttom still the dorimanx logo ?

@ all others,

another good news, carbon guru also gave me the permission to use the logo, so at the moment i'm just sitting at the pacman logo (rework from scratch) and when i'm finished with that i will do the carbon bootanimation :D
[Galaxy S II Android Development] Verna KDM:
I would like one like this for the slimbean without the slim logo.
[Galaxy S II Android Development] thereald:
Ok, well then be patient a lil bit cause I have two others to do 1st, I will inform you when it's done ;)
[Transformer TF300T Q&A, Help & Troubleshooting] noahvt:
Hi guys,

I just wanna ask if there is a way to dualboot android roms because I switch roms alot :\ if we can dualboot android and linux wouldn't it be possible to boot android and android as well?

thanks,

noahvt
[Transformer TF300T Q&A, Help & Troubleshooting] _that:
I am dual-booting a stock-based ROM on internal storage and CM 10.2 on a microSD card on my TF700T.

If there is significant interest, I'll document in detail how to do it - a PC with microSD reader and Linux and some basic knowledge of Linux command line usage is required.
[Transformer TF300T Q&A, Help & Troubleshooting] noahvt:
Can you explain me? I'm running linux on my pc (ubuntu 13.10) :)
[Transformer TF300T Q&A, Help & Troubleshooting] _that:
I documented the procedure here: http://xdaforums.com/showthread.php?t=2501129
[Transformer TF300T Q&A, Help & Troubleshooting] noahvt:
Thank you very much!
[Omni Features Development] Entropy512:
Sometime in the next few days (maybe this weekend), we will be merging https://gerrit.omnirom.org/#/c/1169/

This will allow TWRP to build properly on userdebug builds. As a warning, it WILL break anyone who doesn't have TWRP config in their device tree when it is merged! (You will get errors about missing files in bootable/recovery/res if I recall correctly)

See http://xdaforums.com/showthread.php?t=1943625 for info on various TWRP device tree configurations. At an absolute minimum I believe you will need the device resolution added to avoid breaking your build.

For additional details, see:

Find5:

https://gerrit.omnirom.org/#/c/1633/

Yuga:

https://gerrit.omnirom.org/#/c/1682/ (Depends on fusion3-common changes)

pollux-common (pollux_windy and pollux don't have specific items and just inherit common):

https://gerrit.omnirom.org/#/c/1155/ (Depends on fusion3-common changes)

fusion3-common:

https://gerrit.omnirom.org/#/c/1152/

flo:

https://gerrit.omnirom.org/#/c/1634/

mako:

https://gerrit.omnirom.org/#/c/1635/
[Omni Features Development] MightyBear007:
[MENTION=591147]Entropy512[/MENTION]

Hey there! :)

Add me on hangouts sir:

mightybear007@gmail.com

What about this TWRP configuration for honami?

https://github.com/Omni-Xperia/android_device_sony_rhine-common/commits/cm-10.2

i have built one for pollux and it works
[Omni Features Development] iofthestorm:
Just wondering, does this recovery actually get flashed when installing? I.e. do all the parameters need to be set properly to build the ROM, or just enough to not break the build? I'm already using TWRP and I'm not sure of the right BoardConfig.mk settings but if I'm just trying to port it to my device that shouldn't matter right? Though I noticed there are device trees on the TeamWin GitHub for building TWRP, for my device (n8013) it seems out of date.

Edit: well cool, turned out not to matter and it seems like my build actually booted, I'm pleasantly surprised :D.
[Omni Features Development] Gandalf:
Pretty much what happens is, TeamWin will get a device tree, modify it to be compatible with TWRP, and use that to build for that device. The actual core source for TWRP itself is in a separate repository that is constantly updated. So pretty much its like this : once your device tree is modified to build TWRP for your device during a build, it will build using TWRP source , which is android_bootable_recovery, for omnirom specifically.

Think of it like this: you setup a device tree to say "build TWRP using this source code" . once the device tree is looking for that source code, it'll always build twrp without issues (for the most part). Now the location your device tree looks to is the twrp source itself, which is updated and improved all the time, so if you're device tree is setup properly for tarp, you will have a recovery.img in your out directory after a build that is as up-to-date build of twrp to when you last did a repo sync
[Omni Features Development] iofthestorm:
Ah thanks, that's useful, but not really what I was asking about. I got that part, I just wanted to know if flashing the ROM actually flashes the recovery that was built in tree as well, and it seems like the answer is no (at least for me my recovery didn't change). As such it seems like the main point that Entropy512 was making is that if you don't add the resolution to your BoardConfig.mk the build won't complete, but otherwise it doesn't really matter if you set the other parameters correctly.

The paths I was referring to were the mount points for the internal and external SD, I thought they had changed since ICS but I think they might still have symlinks to the old paths for compatibility's sake.
[Omni Features Development] mo976:
You mention mount points for the SD, I have been building for the HTC One S and while all the mount points in the my ville/rootdir are correct for example in the fstab.qcom file

# SD card

/devices/platform/msm_sdcc.1/mmc_host/mmc0 /storage/sdcard0 auto defaults voldmanaged=sdcard:36

The rom shows it as unavailable/missing and asks me to format the SD card, I tried and the message keeps popping up.

Basically my question is, will building twrp recovery for the device sort out the missing SD card.
[Omni Features Development] Gandalf:
flashing a ROM will never flash a recovery, but some devices have the recovery as part of the boot.img, so when you flash a new kernel, for example, you will be flashing a new recovery as well
[Omni Features Development] Entropy512:
Ideally you should have a goal of building a fully functional recovery.

However, with the exception of older Samsungs (galaxys2 family and older for the most part) and Sonys, you don't NEED the recovery to be fully functional. With the galaxys2 family and Sonys - yeah you need it. (Actually Sonys do have a workaround, but the GS2 family does not.)

That said, leaving a partially configured recovery configuration is bad practice.
[Omni Features Development] iofthestorm:
Yeah, that'd be what I was thinking of. My first Android phone, the Samsung Fascinate, had a weird setup like that.

Alright, that's what I figured. Yeah, I'll fix it later for sure, I just didn't have the time this weekend and I didn't plan on submitting a patch to make it officially supported anyway, as I just wanted to try it out for myself at this point. And I figured since it's the n8013 you'd be the best person to support that anyway, I only know enough to get myself in trouble.

(do you still have your N8013 by the way?)
[Omni Features Development] Entropy512:
I do, but it mostly collects dust these days. At some point I'll try to get Omni up on it, I've just had too much else to do lately.
[Omni Features Development] iofthestorm:
So another question, what is the mechanism by which twrp.fstab is used? I decided to flash my recovery for the heck of it (sidenote: on the 4.4 branch it still has the AOSP recovery in the manifest, but I just added omnirom/android_bootable_recovery to my local_manifests.xml) and it actually runs but nothing appears to be mounted. I notice that some TWRPify commits have a twrp.fstab but they don't do a PRODUCT_COPY_FILES for that file so I'm wondering how it even gets used? I see for example that your commit for flo is doing it: https://gerrit.omnirom.org/#/c/1523/ but then this guy didn't actually add it to PRODUCT_COPY_FILES for hammerhead: https://gerrit.omnirom.org/#/c/1588/ . Is that just a mistake on Mithun's part, or am I misunderstanding how this fstab is used? Is there any reason for it to be any different than the fstab.smdk4x12 in the device tree? Just trying to figure out how things work here.

Also, is it preferable to use the by-name symlinks over the raw /dev/block/mmcblk0p9 type device identifiers? Should I open another thread for this?

My hackjob device trees are https://github.com/ibrahima/android_device_samsung_n80xx-common and https://github.com/ibrahima/android_device_samsung_n8013 .

Edit: I guess my main question is, how is that twrp.fstab different from TARGET_RECOVERY_FSTAB? Some of the device trees with it (eg. your flo changeset that I linked above) don't seem to set this unless I'm looking in the wrong place, and I've seen at least one that sets TARGET_RECOVERY_FSTAB to /etc/twrp.fstab. Found this quote from [MENTION=912474]Dees_Troy[/MENTION]:

from http://xdaforums.com/showthread.php?p=45164117 . If I already have an /etc/recovery.fstab it should work without the twrp.fstab right?

Edit2: Oh, derp, the twrp.fstab explanation is in the "How to Compile TWRP" thread. Filing away for later reading... (this is fun and all, but my professors aren't going to accept an Android 4.4 build in place of my homework ;) )

Edit3: My god, this is basically me: http://xkcd.com/356/ and the truck is my homework/midterms... welp, at least I got a recovery with proper fstab, so for anyone else trying to TWRPify yes, you do need a twrp.fstab because the new fstab format in Android 4.3+ is not used by TWRP yet so you need one in the older format for it to mount your stuff. Haven't actually tried flashing anything with my recovery yet, but I feel like it should probably work, but again... trucks and all that ;)
[Omni Features Development] Entropy512:
If it's not in PRODUCT_COPY_FILES - yes, that is a mistake.

(hopefully that commit isn't merged - accessing omni's gerrit is problematic for me from some locations. If the TWRP FSTAB is added to the device tree but isn't being copied that's grounds for a -1)
[Omni Features Development] iofthestorm:
Yeah, he -1ed it himself for other reasons I suppose. Cool cool, looks like I'm learning stuff :)

By the way, after the hard drive meltdown and subsequent loss of two weeks of gerrit data, a lot of the links in your OP are broken in that they go to different tickets which have now subsumed those ticket numbers that were lost. For those who are curious and have been foiled by Gerrit's somewhat obtuse search box, if you type message:TWRP in the search box (to search commit messages) you'll find examples.