yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] ZeRo2o9:
That kernel is old and doesn't have all the fixes that has been done to cm why are they using it
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Try the new kernel or just stick with the default. Btw what the hell is linaro. Just curious. And not trying to be off topic
[HTC Vivid, Raider, Velocity] rignfool:
Linaro is a tool chain that you use for compiling...

Iirc it tells gcc what to do
[HTC Vivid, Raider, Velocity] jtsurfs:
So can't someone compare what Syn had in his kernel to what we currently have and sort of combine them?
[HTC Vivid, Raider, Velocity] cmerlyn:
The Sultana kernel seems to be making quite a bit of progress, and a fix to the in-call volume is being worked on, but no success yet.

Keep an eye on CM10 development and Sultana development and you will get the fix as soon as they find one. That's what I am doing.
[HTC Vivid, Raider, Velocity] :
Exactly.
[Asus Transformer TF700] grenness:
Sorry for possibly being a noob, but after rooting and upgrading my TF700 to CleanROM (now on 3.2.2) I notice that I no longer have access to my work calendar, running on a Zimbra server.

I also have a stock Samsung Galaxy Note, and on both devices I have set up MS Exchange ActiveSync accounts with correct credentials.

But while on the GNote I can see the work calendar and do realtime sync, nothing appears on the TF700 (but under Settings, Accounts, Corporate, it seems that it syncs the Calendar without any errors (it says "Last synced 14/02/2013 15:44").

Should I just try to remove and add the account again, play with the credentials, or is there a known bug somewhere related to this?

Thanks,

Christopher
[Sony Xperia P, U, Sola, Go] diegonnc:
Download link to 1.3 is not working, it says "invalid link format", i think you missed something there .
[Sony Xperia P, U, Sola, Go] andilien:
Re: [ROM][ALLBs][FAST][SMOOTH]DynaMOD v1.3 FINAL

Edited, Sorry...

Enviado desde mi ST25i usando Tapatalk 2
[Sony Xperia P, U, Sola, Go] andilien:
Its one Top ROM on HTCMania forums
[Sony Xperia P, U, Sola, Go] Equama:
is there any cwm in your kernel?
[Sony Xperia P, U, Sola, Go] Equama:
paid app!!!!!!

why did you give paid app in your rom??? pls remove root explorer and upload. it's against forum rules.

feedback:

*no cwm with kernel

*android keyboard force close

*no English systemui???????

*systemui not working properly??????

*some bloatwares

*lags while scrolling
[Sony Xperia P, U, Sola, Go] bevoc:
bug

keyboard crashes when change language to eng us
[Sony Xperia P, U, Sola, Go] andilien:
Sorry, but This ROM has been created for HTCMania forums, and the default language is Spanish

Im creating An update for english version
[Sony Xperia P, U, Sola, Go] leos0000:
Put russian lang please bro
[Sony Xperia P, U, Sola, Go] Nephentos:
Luce prometedor

Luce prometedor, pero tantos arreglos visuales me hacen pensar que consume más ram...

Podrías postear un récord de rendimiento?
[Sony Xperia P, U, Sola, Go] andilien:
Te puedes pasar por HTCMania y ceras la fama que tiene esta ROM, y las buenas opiniones que tiene

Enviado desde mi Xperia U usando Tapatalk 2
[Sony Xperia P, U, Sola, Go] SpaceCaker:
Stuff missing on your first thread

Something that u need to post according to xda rule

Credits and links to stuff u used :p
[Sony Xperia P, U, Sola, Go] leos0000:
How I can change font man?
[Sony Xperia P, U, Sola, Go] andilien:
Using font changer

Enviado desde mi ST25i usando Tapatalk 2
[Sony Xperia P, U, Sola, Go] Elwino2.3:
You must use English. According to XDA Rule ;)
[Sony Xperia P, U, Sola, Go] underskyzx:
v1.3 download link says:

Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
[Sony Xperia P, U, Sola, Go] andilien:
Use 4shared mirror

Enviado desde mi ST25i usando Tapatalk 2
[Huawei Ideos X5 U8800] jermasta:
Hi,

I was trying to update my huawei u8800 pro from 2.2 to 4.0 soft.

I downloaded the software from huawei.com

During 1st step of installing the proces stopped.

I have tried more times to put the phone to a pink screen, but nothing happend.

I also have tried make it through comp with battery outside or installed battery, but no way.

Pls, could you someone help me?

Thx
[Huawei Ideos X5 U8800] trojan_hors:
Check this if it helps http://xdaforums.com/showthread.php?t=2017237
[Galaxy Note II Q&A, Help & Troubleshooting] ksc6000:
I don't see Samsung acknowledging anywhere that 4.1.2 fixes SDS. I see a bunch of samsung/android websites ASSUMING as such, but no proof.

The exynos exploit? Yes. But I'm thinking that we're all assuming 4.1.2 is SDS safe.

I'm starting to think that there IS no fix. Samsung doesn't even want to acknowledge it. The only fix is being on the new chip (07).
[Galaxy Note II Q&A, Help & Troubleshooting] UtkarshGupta:
No phones with dll7+ have been reported to have sds. So theoretically it does patch it.
[Galaxy Note II Q&A, Help & Troubleshooting] ksc6000:
Exactly. We're just assuming. So theoretically we could be wrong, and someone could be enjoying better battery life on 4.1.1 and have the same exact risk exposure as we do.
[Galaxy Note II Q&A, Help & Troubleshooting] UtkarshGupta:
No.

All the cases of sds have been on 4.1.1 roms. Non on dll7 ones.

4.1.1 is highly vulnerable.

Why do you even take the risk.

The glass is half full not half empty.

Be optimistic and not pessimistic.
[Galaxy Note II Q&A, Help & Troubleshooting] ksc6000:
You're missing the point. I'm not going to downgrade to 4.1.1, because I'm worried, just like you.

The point is it seems to me that we are throwing around 4.1.2 as FIXED, when it possibly might not be. On this forum we are saying that it is FACT, when it seems to be just assumptions. I believe that's a possible false sense of security we are giving people. I feel that's harmful. We should encourage people to upgrade to 4.1.2, but we should say "it seems the SDS bug is fixed in 4.1.2", not that it IS, when we don't know for sure.
[Galaxy Note II Q&A, Help & Troubleshooting] koalauk:
Somewhat I agree
[Galaxy Note II Q&A, Help & Troubleshooting] dr.ketan:
Samsung officially never say it, so i don't think without this some one stamp it. (bcoz this time patch done by themselves, if xda developer have did that then surely they can stamp)

At least myself always use words 'its believed to be fixed for sds'

Now why should we believe

-kernel from ll7 and later have found to have that insane chip version mentioned in its source code(which was never there before) , that strongly suggest samsung have made something patch for that chip, so when kernel found such chip may block issuing such commands

-we have not seen any sds case on those latest rom which believed to have patched for.

PS : if you aware of brick bug on Note1 and s2,there was also related to mmc chip and wiping command was causing brick, samsung till today never acknowledged (or accepted) it was there and thousand bricking case reported

And there was not a single case was reported after kernel was patched by xda developer. (chainfire, philz, hydrocore, soeedmod are examples)

Ultimately when samsung released jb leak, it found samsung have patched it, and somewhat agree with developer in personal communication. So it's samsung policy, I don't expect they will ever do it. Disappointing but true.
[Galaxy Note II Q&A, Help & Troubleshooting] ksc6000:
So essentially what you're saying is that it appears samsung has fixed it in 4.1.2, but they will probably never acknowledge it? Am I reading that right?
[Galaxy Note II Q&A, Help & Troubleshooting] dr.ketan:
Exactly,

B'coz acknowledging it is indirectly accepting they have used faulty chip. :p
[Galaxy Note II Q&A, Help & Troubleshooting] or1onz:
Mine just died yesterday, N7105 running on 4.1.2.

Not sure the kernel though.

Passed it to Samsung care today. They said they will change the motherboard and .. it will take around 2 weeks as their motherboards are out of stock. So you can imagine the number of spoiled note 2.

From Singapore btw~
[Galaxy Note II Q&A, Help & Troubleshooting] FloatingFatMan:
Samsung will never acknowledge the SDS issue. Doing so would open them up to one hell of a mess in lawsuits from pee'd off customers.
[Galaxy Note II Q&A, Help & Troubleshooting] aka_sirok:
actually it just fixes the issue if you update before having a corrupted chip. There were lots of reports of 4.1.2 died phones but we assume that it is because, as they said, the phone was having problems before updating.

hope my explanation helped you, bests
[Verizon Samsung Galaxy S III] maoq2:
hello, i just recently bought a Samsung Galaxy S3 SCH-i535 From Verizon, but im living in Dominican Republic, i unlocked it!, but i can't set the apn configuration!, when i press the menu key it just say, Reset the default configuration, when i do it, it says that has been resetted correctly, but there is nothing on the screen, and i can't navigate unless i connect into a wireless connection, i flashed the cellphone to the Stock Firmware and i can't use my internet data, what can i do?:(
[Verizon Samsung Galaxy S III] oilfighter:
Here's what I've gathered, but since I haven't tried it out myself, I can't verify that it will work. As I am about to go overseas and use a local SIM card, I would really appreciated if you could try it out and respond back with the result.

* Step 1. Go ahead and install the apps APN Manager, Titanium Backup, Titanium Backup PRO, and Phone info app from Play Store. APN Manager and Titanium Backup PRO apps are pay apps but totally worth it if you want to turn your Verizon GS3 into World phone. For Titanium Backup app, you need to download both the free version and PRO key.

* Step 2. Next open up Titanium Backup app, hit the “Backup/Restore” tab and choose “APN Manager Pro”.

* Step 3. Swipe to the right.

* Step 4. Choose “convert to system app”.

* Step 5. Next, open up APN Manager Pro app and choose “Insert APN”.

* Step 6. Insert the APN settings for the country’s carrier you are traveling to. Google “Carrier APN settings”, replace “Carrier” with the carrier name of the country. For example, if you are going to use Prepaid SIM on UK’s Orange, google for “Orange APN settings”. Then you will want to input that APN info

Source: http://pc-updates.blogspot.com/2012/10/how-to-turn-your-rooted-verizon-galaxy.html
[Verizon Samsung Galaxy S III] Wrngway:
As I understand it you can use a 3rd party foreign sim by activating the global roaming feature on your account online. Then in mobile settings changing your network mode to global. You may not have data though. My wife was able to do this when in Thailand. Her phone isn't rooted or unlocked.

If you're rooted you may be able to activate data by inputting the APN using the method described above. Please let us know if this works!!
[Verizon Samsung Galaxy S III] oilfighter:
To answer my own question, the steps I posted worked perfectly on CleanRom 5.6 (Jelly Bean based). I was able to use GSM 3G at HSPA+ speed on a local SIM card in Taiwan.

Now, does anyone know if I have to do anything when returning to the states?
[Verizon Samsung Galaxy S III] johndguez:
3G or 4G in Dom. Rep.?

Hi, I would like to know if it will works 3g or 4g in Dominican Republic after follow this steps and applying this settings?, bands on my country are 850/900, thanks
[Nexus 7 General] stevemoffler:
So goofing around I tapped repeatedly on build number and it said I was "two steps away from being a developer" so I tapped on it a few more times and it said "you are now a developer" wth lol

Sent from my GSIII
[Nexus 7 General] br0adband:
That's how you enable Developer options in Jelly Bean - tap the build number 7 times.

Learn something new every day, doncha? ;)
[Nexus 7 General] stevemoffler:
I never knew that lol

Sent from my GSIII
[Nexus 7 General] bclark:
I accidentally thanked you so I guess I have to bust your bubble and let you know that's how you enable dev options in the settings menu and its a jelly bean feature that "almost" everyone knows about
[Nexus 7 General] ynrozturk:
What is the point of this thread? 99% of the people here know this already.
[Nexus 7 General] cnstarz:
welcome to 2012.
[Nexus 7 General] knuckles1978:
I was 34, got old, and told my grandchildren about that the other day.
[Nexus 7 General] stevemoffler:
I didnt know about it so woah your horses troll

Sent from my GSIII
[Nexus 7 General] cnstarz:
how about you "woah your horses" before making a stupid thread like this and expecting non-troll replies.
[Nexus 7 General] luis86dr:
Developer? What's that?
[Nexus 7 General] kieso:
Welcome to aholeville Steve. People are so kind here
[Nexus 7 General] etirkca:
0/10

Derp thread
[Nexus 7 General] knuckles1978:
Its what they do when you take your 35mm film to the man (or woman of course, let's not be sexist) in the shop.
[Nexus 7 General] stevemoffler:
The reply wasnt even towards you but if you are offened by it and felt the need to reply and be a douche. Then be my guest and take your ass off this post...

Sent from my GSIII
[Nexus 7 General] knuckles1978:
Take a joke eh, no need to get those panties in a twist now. And pick that bloody dummy up while you're at it. You've made yourself look stupid enough for one day lol
[Nexus 7 General] nodstuff:
For a second there I thought this thread was gonna be all nice comments, thank the flying spaghetti monster I read on after the second post.

@OP
[Nexus 7 General] DeadlyDazza:
Inb4 lock
[Nexus 7 General] Divine_Madcat:
Indeed...
[Samsung Galaxy W I8150] TiTAN-O-One:
How do you guys port ROMS from other phones? If you know, be my teacher... I remember my purpose of coming to XDA

is to make everyone happier with their devices so i thought PORTING was good enough! LoL :cool:
[Samsung Galaxy W I8150] stpdkid:
this is a guide for you.

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

good luck buddy:)

-if it help, just press thanks-
[Samsung Galaxy W I8150] TiTAN-O-One:
Thanks eh mate! Managed to Port ROM, but got bootloop... :( I'll go see whats the prob! :cool:

Sent from my Moms STOCK Mini 2 :((
[Samsung Galaxy W I8150] stpdkid:
greatt..soon we'll have another dev:)
[Samsung Galaxy W I8150] TiTAN-O-One:
I thought a person who PORT ROMS is a POTTER? :what:
[Samsung Galaxy W I8150] miki2o:
No, is a porter. LOL
[Samsung Galaxy W I8150] stpdkid:
it start with porting..
[Samsung Galaxy W I8150] afif_7070:
n those who love to flash call flasher?lol..
[Samsung Galaxy W I8150] TiTAN-O-One:
Hmm... All XDA community will have a special power.. Called MASS ROM FLASHING :D:D:D
[Samsung Galaxy W I8150] coliv_aja:
What rom you want to port?
[Samsung Galaxy W I8150] TiTAN-O-One:
The first stripped down Sense PORT made for our Wonder!:D

Currently planning to Develop a CM9 Based ROM :3
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] howard bamber:
Hi I want to send my GF, in the USA an unlocked international note. I day it will work on at&t, the guy in the shop says no. It's the N7000

Thx

From box 13......
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] warfareonly:
It will work as long as it supports the frequencies.At&t is gsm so it should be compatible. Just check if the frequencies are supported.

P.S.: remove the comma after gf
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AndroidSlave:
I have an unlocked German gt n7000 I got from amazon. I am in los Angeles. It works perfectly on at&t. Just download at&t messages app from the web and side load it, and you will get visual voicemail for free too. You must use the WAP.Cingular apn

There is a thread here about it. Search.

---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------

If it is truly unlocked it will work
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] TheNoticer:
AW: Will an unlocked uk note work on at&t?

Wrong section
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Geekybiker:
Works great. Lots of people using ATT's network either natively or through straight talk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I'm trying to find a bug list for CM10.1 nightlies for the GSIII AT&T. I did a search, but I couldn't come up with anything. Is there a thread about the main CM10.1? All I see are other people's versions of it.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
I don't think there's a specific bug list. Although, there are changelogs and features list. It pretty much acts as the same ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
gotcha. i couldn't find a specific thread for it in the development section so i wasn't sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Cm development is in original development.

The nightly changelogs are http://mobile.10.1.cmxlog.com/?device=d2att#cm-10.1-20130120-NIGHTLY-d2att.ziphere
[Sony Xperia T, TL, TX, V] lilstevie:
LK for Xperia T

LT30p Only - Unlocked Bootloader Required

WARNING 1: This modification makes changes

to the devices partition table. I (lilstevie) am not

responsible for any damage to your device or

data loss that may occur.

WARNING 2: ICS kernels currently do not boot

with this modification at this point in time. This

can only be used with JB kernels including those

from the alpha and leaked releases. At the time

of writing the TWRP 2.4.1.1 FOTA image has

everything required to boot without any changes.

Since getting the Xperia T the biggest annoyance is only having one bootable partition.

To combat this issue I have spent some time porting the Little Kernel bootloader. This

allows booting different kernels for recovery and boot as well as a full implementation

fastboot.

Features:

Separate boot and recovery partition.

Full fastboot implementation including fastboot boot (with correctly formatted boot.img)

Ability to load both Android boot image and sony elf formats.

Boot to recovery, and boot to recovery from userspace (requires patched kernel).

Known Issues:

No display until kernel has booted – This is also the case with S1Boot.

Cannot reboot into another boot mode without kernel patch.

No LEDs to indicate status.

ICS 3.0 kernels will not boot.

Usage:

After 1 second from pressing the power button LK will listen for input on the volume keys for 2-5 seconds:

Volume Up -> boot recovery.

Volume Down -> boot fastboot.

Credits:

Rebellos -- Inital work on getting eMMC and buttons working.

Dees_Troy -- extract_elf_ramdisk served as a base for elf parsing.

cdesai -- Bug fixes and hosting bootloader on his github.

Various others for support, if you think your name should be here

and that I have forgotten all about you let me know.

How to install LK:

Download LittleKernel-1.0-FINAL.zip

Copy LittleKernel-1.0-FINAL.zip to device

Boot into recovery

Install LittleKernel-1.0-FINAL.zip

How to install LK ready kernel:

Download JB_Kernel_LK.zip

Copy JB_Kernel_LK.zip to device

Boot into recovery

Install JB_Kernel_LK.zip
[Sony Xperia T, TL, TX, V] lilstevie:
Versions:

Version 1.0:

Initial Release.

MD5Sums:

LittleKernel-1.0-FINAL.zip - fd550025493533db904ecb5bc299ac9b

JB_Kernel_LK.zip - cc185b728e28865fe6323f4cc96e17a0

Building a boot image for lk should be done with the

following boot image settings:

Base Address: 0x80200000

Ramdisk Address: 0x81400000

Page Size: 2048

Cmdline: “user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 kgsl.mmutype=gpummu”

Copyleft:

LK here.

Kernel here.
[Sony Xperia T, TL, TX, V] lilstevie:
reserved for future use
[Sony Xperia T, TL, TX, V] cdesai:
:D
[Sony Xperia T, TL, TX, V] tilal6991:
Sweet. I saw the patch on gerrir and was wondering how it worked. Will have a try.

The only thing I'm wondering is whether there is a way to reverse the changes to the partition table.
[Sony Xperia T, TL, TX, V] DooMLoRD:
Very interesting... Awesome work guys...

And good to see cdesai around ;)

I am still unclear on few things though..

Ok so from what I understand you are still depending on s1boot as primary bootloader. Then once the primary bootloader passes boot sequence to main kernel (mmcblk0p4) you have little kernel which will intercept it and then function as a bootloader? Which can then accept these commands or in turn boot a secondary kernel (fotakernel) or mmcblk0p16 which will now act as boot partition for the OS?

My concern is how are you making space for that mmcblk0p16? Are you repartitioning internal sdcard?

I think flashing a standard full stock firmware should restore partition table
[Sony Xperia T, TL, TX, V] cdesai:
There is 300mb free space at the end of the emmc, and this makes a new 30mb partition after the sdcard.

Like you said DooMLoRD, s1boot is still used, and it loads lk which in turn loads p16 as kernel, and p11(FOTA) as recovery.

There's still enough space left to add more kernels, and some sort of a boot menu to multi boot :)
[Sony Xperia T, TL, TX, V] lilstevie:
We can't actually replace S1Boot due to code signatures, and S1Boot is actually multiple bootloader stages in 1. Other devices would have pbl sbl and appsboot.mbn, Sony have combined them all into 1, LK is only a replacement for appsboot, thankfully between each stage everything that was turned on gets turned on for the purpose of appsboot (such as mmu) get turned off again before the next stage which allows us to do this without major hacks. Essentially what we are doing is adding an extra boot stage.

mmcblk0p16 which has been added to the end indeed does act as the new boot partition. I did originally plan to add another extra partition for boot, but after talking to Dees_Troy we worked out a situation where we could utilise FOTAKernel for recovery and not impact installation of TWRP from goomanager.

I do understand this concern, however I did notice that all Xperia T's that I have encountered so far (I checked with ~10 peoples devices) and they all have 300±25MB of unused, and unpartitioned space at the end of their eMMCs, I do not delete or resize any partitions. This is the script I run when installing lk if you are interested in seeing how it is done.

Utimately this is what eased my feelings towards modifying the partition table, I understand people get a little bit funny about things that cannot be easily reverted, and in this case flashing a stock ftf or using EMMA to reflash back to stock will undo the changes to the partition table.
[Sony Xperia T, TL, TX, V] lilstevie:
Please contact me if you have any of the following devices with a bootloader unlock: Xperia TX, TL (Are any of these unlocked?) and V. I would like to add support for these devices but as I do not have any of them I will need some testers.

EDIT: Xperia V is off the table for the moment as there isn't enough free space to remap the kernel partition.
[Sony Xperia T, TL, TX, V] travis82:
Have a tx unlocked
[Sony Xperia T, TL, TX, V] lilstevie:
from recovery can you please run "parted /dev/block/mmcblk0 unit MB print free" and paste the output for me.
[Sony Xperia T, TL, TX, V] travis82:
parted /dev/block/mmcblk0 unit MB print free

Model: MMC MAG2GA (sd/mmc)

Disk /dev/block/mmcblk0: 15634MB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

0.02MB 0.13MB 0.11MB Free Space

1 0.13MB 2.23MB 2.10MB TA

2 2.23MB 3.80MB 1.57MB Boot

3 3.80MB 5.37MB 1.57MB Boot2

5.37MB 6.29MB 0.92MB Free Space

4 6.29MB 27.3MB 21.0MB Kernel

5 27.3MB 28.3MB 1.05MB TZ

28.3MB 29.4MB 1.05MB Free Space

6 29.4MB 32.5MB 3.15MB modemst1

32.5MB 33.6MB 1.05MB Free Space

7 33.6MB 36.7MB 3.15MB modemst2

36.7MB 37.7MB 1.05MB Free Space

8 37.7MB 40.9MB 3.15MB fsg

9 40.9MB 46.1MB 5.24MB ramdump

10 46.1MB 54.5MB 8.39MB ext4 apps_log

11 54.5MB 71.3MB 16.8MB FOTAKernel

12 71.3MB 1359MB 1288MB ext4 System

13 1359MB 1621MB 262MB ext4 Cache

14 1621MB 3769MB 2147MB ext4 Userdata

15 3769MB 15634MB 11866MB ext4 SDCard

Makes me wanna do what I did with the Note and redo the partition format and add a bit more space to the sdcard partition. So lets say we use CM rom. Couldn't we just remove the fota partition a boot partition, ram dump, apps log, etc.. and add the extra to the sd or data partition.

So the main question is I guess what partitions does the phone need to run aosp so we can use the extra space somewhere more useful?