yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] howardsl2:
Thanks for the responses. Are you still having issues booting into the ROM (stuck on the Android logo)?

If so, please try to flash it again. Make sure that you load the parameter file and select all seven checkboxes *including* the parameter.txt for flashing. Don't forget to Erase IDB first.

Your Android stick should auto-reboot right after the flashing is done. Therefore, it is recommended to connect the USB power cable (if you have a spare one) while flashing, and when finished, let the Android stick initialize for some time before unplugging it from power.

Let me know if you manage to get it fully working!
[Android Q&A, Help & Troubleshooting] howardsl2:
** Update **

An issue with the new ROM was identified and fixed as of 7PM UTC on 05/18/2015. The updated ROM containing the fix had been uploaded. If you downloaded the ROM prior to the date/time above, please re-download it from the link in the main post and follow the instructions again.

All flashing instructions have been tested on my own device and confirmed working.
[Android Q&A, Help & Troubleshooting] cracktrix:
Thanks man!!! I've downloaded the rom , and I'll try to test in my TV Stick tomorrow. I tell you after how it goes me. Thanks very much.
[Android Q&A, Help & Troubleshooting] oofnik:
Thanks so much for posting this. I finally managed to un-brick my TV stick and get it working again, now with real 1080p!

I used RKAndroidTool v1.37, entered the offsets manually from parameters.txt according to your file and everything flashed successfully after hours of repeated attempts to flash various other ROMs. Originally I was trying to flash Pi****u Linux but thought I bricked the device. Turns out I didn't. Thanks again!

Which brings me to an unrelated question... has anyone successfully booted this device from SD card?
[XDA Assist] M.elec:
Dears

I have a problem with my Galaxy Note II (GT-N7100) that suddenly white screen and color freckled

powering on shows pure white screen (Pic 01)

powering on recovery mode (Vol Up+Home+Power) shows color freckled white screen (Pic 02)

powering on download mode succeeded .... power off by hold power button will power off then after ,few seconds , powered on showing download mode screen but color freckled (Pic 05)

noting that it has official rom and the version is Jelly Bean but I don't remember the exact version code

sorry about my weak language

Thanks in advance
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. It looks like it's a hardware problem and software is not going to solve it. Are you still under warranty? If so now is the time to claim the warranty. If not you're going to have to take it to a phone repair shop.
[XDA Assist] M.elec:
Thanks for quick response..... The phone is out of warranty... Also I have sent it to the repair shop but they are incapable of repairing it.... You can close the issue ...

Thanks and best regards
[Sony Xperia T, TL, TX, V] Jeremy183:
So i have the Sony Xperia V (LT25i) and tried to find my way to CM and rooting and all this cool stuff apple users can't get..

I'm also new in this forum but i searched my problem and didn't find anything, if anyone knows more just send the link to the thread and thats it.

I rooted, got bootloader unlocked and tried to flash cm, bricked my phone, somehow got access to the flashtool again and flashed a stock rom, made a factory reset and i think thats all i messed around..

But the problem is now that some apps can't access the internal storage properly for example:

-can't download or upload media in whatsapp

-can't put homescreen via album app (external sd card not found)

i think that's it for now

I hope someone can help
[Sony Xperia T, TL, TX, V] jd1639:
Hi, thank you for using XDA Assist. The best place to find an answer is in your device's specific forum. See this, http://xdaforums.com/xperia-t-v
[Sony Xperia T, TL, TX, V] Jeremy183:
Nooby me..

So just post the same thing in another thread or do you push it there?

I Don't want to spam the forums with my threads and stuff....

Thanks for the reply!!
[Sony Xperia T, TL, TX, V] jd1639:
I'll ask a moderator to move it there. Here's where it'll be moved to, http://xdaforums.com/xperia-t-v/help
[Sony Xperia T, TL, TX, V] sublinker:
Go to Settings/Apps/All, find "Media Storage" and "Clear Data" button, and then restart your phone.

If that doesn't work backup your files and format the SDcard in Android.
[XDA Assist] Kh4zy:
Hi xda!

I have a python script that I got running on my Samsung Galaxy S I9000(Rooted). The script is working 100% so far, except that my python script stops when trying to either disable or enable the 3G data.

class Eov(object):
def change_IP(self):
print("Changing IP")
os.system('su -c "svc data disable"')
sleep(20)
print("Data Disabled")
os.system('su -c "svc data enable"')
sleep(20)
print("Data enabled")
print("IP has been changed")

I have no clue what to do. The script just stops when it comes to disabling the data network. Its gettign disabled and then it stops. Not like stopping the script, but it somehow freezes/getting stuck?
[XDA Assist] Razvan:
Hi there,

The best place for this device specific question is here:

Galaxy S Plus I9000 Q&A

Galaxy S I9000 Q&A, Help & Troubleshooting

Good luck
[Sony Xperia M2] iFlashed:
This post is closed. All developers had been informed and I think this thread is not explained as it must be (is not a thing of aquas only). Just two different sensors in each device...

https://github.com/sonyxperiadev/kernel/issues/353
[Sony Xperia M2] linuxct:
However it's not something exclusive from Aqua, but also for some other models like D2303 in the 'new period' as you can see here: http://xdaforums.com/showpost.php?p=60797370&postcount=192 ;)
[Sony Xperia M2] aidy.lucas:
I thought the normal m2 was the same, it must be a model revision due to the Accelerometer bug that has been affecting certain production runs. Gonna find out when mine was made had it since beginning of Sept last year not had this bug yet

D2303 stock deodexed 4.4.4 KK rooted philz touch recovery xposed Bravia engine 2 x-reality
[Sony Xperia M2] galaxyfreak:
Nice one [MENTION=4787101]linuxct[/MENTION]! :)

Development wise, for custom ROMs here, not much, but atleast 3.4 Omni, you could find one with old accelerometer, and one with the new accelerometer. See what firmware version they run out of the box.

After that, download matching kernel archive from Sony's website, and check difference in accelerometer driver.
[Sony Xperia M2] iFlashed:
Sounds interesting!

I'd like to do it. But unfortunatetly, I dont' know too much of ROMS, and I don't know exactly for compare the accelerometer drivers and do it compatible with custom roms :(
[Sony Xperia M2] linuxct:
I've tried to do it. But I don't find any accelerometer driver in Sony's archive (?) :eek:

Also, exams are very close... Might try again after finishing :D
[Sony Xperia M2] galaxyfreak:
drivers/input/misc/kionix_accel.c
[Sony Xperia M2] linuxct:
Oh thanks, I was actually looking for an 'accel' folder :silly:. As I said I will try after exams ;)
[Sony Xperia M2] galaxyfreak:
[MENTION=4787101]linuxct[/MENTION] Now when panel on new models and Aqua is solved, before I pull the trigger (add Aqua models to OTA assert, so you can flash the zip), I wanted to look into this.

I don't seem to have accelerometer (kxtj2) on any input. And I'm sure it's working.

How am I supposed to debug this :P

getevent:
[Sony Xperia M2] linuxct:
Oh, wow. And also you have the gpio-keys placed in event5, it's the first time I see this.

However I must say, the person who had the event7 problem is [MENTION=6487599]iFlashed[/MENTION], not me, as I have old D2303, with event6. I only helped him to discover what was wrong.

Now, if the accel is not placed in any event, then how is it working? Other way of input ??

I'm checking in my device and there's not kxtj2 nor accel... event3 throwed an out-of-memory error btw.

Tell us what to try/do and we'll try.
[Sony Xperia M2] galaxyfreak:
stock 3.4 and 3.10 have very different sensor implementation.

How did you relate bootloops on Omni and CM12 with sensors.
[Sony Xperia M2] AleksJ:
Information for shifted gpio-keys is known by more than two months.

source
[Sony Xperia M2] linuxct:
They found before... LOL

That's the problem of local forums, people have to discover things twice if they don't publish it in global-english forums like this one.

However, we still don't know why Sony did this... I can't understand them.
[Sony Xperia M2] AleksJ:
Yes, and that was the reason for the changes, and why they were made hardly anyone here can say with certainty.

What does it matter forum or palace if problem still exist ?

btw, they already published here ;)
[Sony Xperia M2] linuxct:
What he published didn't work tho, as iFlashed device uses event7 and inside!out give him a boot.img with event4 in bootrec-device

If sony could give us any explanation on why they did this...
[Sony Xperia M2] erikcas:
messing with sensors in 3.10 will not work. It will probably lead to more bootlooping.

Could you try this workaround? it is sony's stock solution for inputdevices.

https://github.com/android-legacy/a...mmit/491bb77288a5941eba7bdd14fbf5d28470971f0b

you will have to implement it in 3.10 kernel. If you cannot succeed pm or gtalk me, I will do

keep in mind it is a workaround. If this works out, well, with my truly panel fresh in mind, we have to check for a proper solution to get it in sxd kernel.
[Sony Xperia M2] erikcas:
It is probably a hardware mounting things. A lot of electronics have to be mounted in a small device.

If hardwaremounting changes because of using another part for whatever reason (innoluxpanel is mounted up-down, truly is not), that has consequences for programming hardware in kernel. (innolux is flipped up-down in paneldriver, truly is not in de same driver).

Using different hardwareparts for same model is quite common in phones.

It kind of surprises me that no users haven't complained about a sensor not working. In the kernel there is another sensordriver present (bma250 if I remember correctly) which is compiled for eagle, but not fixed yet. Apperently there is still no user who has this particular hardware part in his phone and we (untill now) all share the same sensor hardware so it functions for everyone
[Sony Xperia M2] linuxct:
Nice. I just contacted you through Hangouts.

Thanks!
[Sony Xperia M2] galaxyfreak:
Means nothing, bootrec-device is no longer used with new recovery.
[Sony Xperia M2] linuxct:
Yeah, true, but I was just showing what was the problem with prebundled recoveries in boot.img... ;)
[Sony Xperia M2] Th3 Ant:
Any updates?

Hi guys

So have you already solved this problem? I have D2303 with those new input events. Cannot boot any custom rom because it bootloops at start.

But now when Sony released those new bootloaders and we can flash recovery images that don't depends on flashed system, new gpio keys are not needed to boot into recovery. So what we need to do to make new devices booting into systems like CM12 or AOSP?
[Sony Xperia M2] iFlashed:
(DELETED)
[Sony Xperia M2] NoobZik:
Still nothing ?
[Sony Xperia M2] SharxX8:
Well galaxyfreak said there s an upcoming solution. Don t know more than that, too...
[Sony Xperia M2] Konstantinosj77:
I found this on [MENTION=985241]erikcas[/MENTION] github,so the solution must be close enough

https://github.com/erikcas/android_...mmit/3d325eb30e76240dbed8a119488433c3a679e1bd
[Sony Xperia M2] erikcas:
Not tested yet. Also working on input fix.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Sony Xperia M2] Konstantinosj77:
Are you gonna release something for testing or it will be an internal test?
[Sony Xperia M2] erikcas:
First I need to test if it behaves like I expect it to. After that testers are welcome. You know how to find me on gtalk?
[Sony Xperia M2] Konstantinosj77:
No i don't know

I dont have the "new" gpio event

but i like searching for bugs
[Sony Xperia M2] Th3 Ant:
I have the new gpio event (D2303) and I can be a volunteer ;)
[Sony Xperia M2] NoobZik:
Same here, I volunteer
[Sony Xperia M2] erikcas:
if you are willing to install aosp, not afraid of the device still in a bootloop, and you are capable to pull a dmesg from adb, pm me

Please, only if you know how to flash with fastboot and if you can use adb, because I need logs!
[Sony Xperia M2] iFlashed:
He is looking for people who has accelerometer problem (gpio event7), because this devices has bootloops. In yours should works because you have old accelerometer.

Enviado desde mi D2403 mediante Tapatalk
[Sony Xperia M2] erikcas:
I donot think the accelerometer is the issue for bootloop.

Verstuurd vanaf mijn Xperia Z1 Compact (AOSP) met Tapatalk
[Sony Xperia M2] erikcas:
To all who pm'ed. We have tested. Still bootloops. When sensorhal is removed the device boots and vol down works.

The problem is probably not in the sensordrivers of the kernel. We have tested with all sensors in kernel disabled but still bootloops with sensor hal.

2 scenarios left:

1. The problem is in kernels input device driver

2. The problem is in sensor hal

Tomorrow the hard labor continues

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Sony Xperia M2] NoobZik:
Well, that's a step ahead for fix at least. In my opinion there's something wrong from the sensorhal since the device become bootable after removing it...

Is anyone tested with the KitKat sensorhal? (My Cygwin won't extract system file from AOSP...)

Sill looking for a volunteer erikcas?
[Sony Xperia M2] erikcas:
Does not work either.

Verstuurd vanaf mijn Xperia Z1 Compact met Tapatalk
[Sony Xperia M2] erikcas:
This is a very nasty thing to solve. As far as it comes to kernel I am out of options. My bet is the problem is in the lib provided by Sony.

Verstuurd vanaf mijn Xperia Z1 Compact met Tapatalk
[Sony Xperia M2] SharxX8:
If so, is this something that is likely going to be fixed with their Lollipop update or is it just going to be the same thing as now?

Seems like I really should ve gotten a different phone :(
[Sony Xperia M2] NoobZik:
There's something fishy....

CM11 Alpha 2 From galaxyfreak boot up sucessfully

CM11 from 4PDA lead me to bootloop (cam fixed)... That's strange...

Something happened between the 30 October 2014 and 18 December 2014...

Need to compare the sources of Galaxyfreak and freak and check what is wrong on the code
[Sony Xperia M2] galaxyfreak:
[MENTION=5712802]NoobZik[/MENTION] probably freack was using unified and i was using stock kernel.

However, biggest problem here is

A) Not being able to confirm for sure 100% which sensor causes issue

B) all devs, incl. Jerpelea have old models

Poslano s D6603 putem XDA Forums
[Sony Xperia M2] iFlashed:
Only SONY knows that...
[Sony Xperia M2] NoobZik:
[MENTION=4635923]galaxyfreak[/MENTION] [MENTION=985241]erikcas[/MENTION]

I don't know if it could help but at the official kernel source here https://github.com/sonyxperiadev/ke...RB1.05.00.02.019.067/drivers/iio/magnetometer

The kxtj2.c is missing compared to the OMNI forked sources...

https://github.com/omnirom/android_...d61f/drivers/staging/iio/magnetometer/kxtj2.c

You said that you had used stock kernel. Was it compilled from sources or did you replaced the ramdisk?

Still searching ...
[Sony Xperia M2] erikcas:
You are looking in the wrong dir. Check drivers/staging/iio/magnometer of the current branch.

For ramdisk: It is produced from sources by android buildsystem so I donot use other, custom or old "prebuilt" ramdisks

Verstuurd vanaf mijn Xperia M2 met Tapatalk
[Sony Xperia M2] erikcas:
https://github.com/sonyxperiadev/kernel/issues/353
[Sony Xperia M2] erikcas:
updated the issue on github. We found out, that in case of bootloop different compass hardware is used. That is corrected now, i.e. the kernel inits the driver fine. I did a pull request for it to sonyxperiadev kernel.

It still does not solve the bootloop issue. I think the sensorhal needs review.

Big thanx to [MENTION=5185525]Th3 Ant[/MENTION] for all your big efforts here!
[Sony Xperia M2] NoobZik:
We're stuck at SensorHAL for the moment...

But the great thing is that you have found the other issue of bootlooping
[Sony Xperia M2] hyshys:
Hi!

Im not sure if i understand this right.. I've been struggling with bootloop errors now for 6 months and have not resolved the problem.

I've tried many different custom roms and setups, have tried PCC restore, have tried installing rom from Emma and only one has worked;

PACMAN rom from early beta stage and it has several errors also.

Can some1 pls tell me what i can try to get any rom working without errors? I've unlocked BL, and i cannot lock it anymore (i think it has something to do with Emma's Open device upgrade). I cannot flash FTF with flashtool coz it has 2 errors: Loader.sin causes flashing abort or loading system.sin causes phone to boot and canceling flash...

Im all out of options here, i've spent too many hours to google and find **** from here but i just cant get this phone work with any CM, AOSP or STOCK.

I just recently got philz multirecovery to install, but i can only get to TWRP for some reason. Other recoverys work pretty good, but 4.4.4-13 cannot find my SD-card.
[Sony Xperia M2] aidy.lucas:
Have you updated the bootloader via Emma, as this did stop locked bootloader devices downgrading firmware if I remember right

http://xdaforums.com/showthread.php?p=61650732

D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
[AT&T HTC One (M9)] Jayanyway:
Alright, so, I converted my M9 from AT&T stock crap to the wonderful world of Developer Edition. On my M8, battery life seemed golden after doing the same thing. But on my M9, I seem to drain hella quick. What I'm noticing is that my Google Play Services is taking up most of the battery life. Just wondering if this is normal or maybe I did a bad convert?

I've already factory reset my phone about 3x since the conversion (I have a mental problem, I reset my phone every few months) and the problem seems to be persistent. I don't use any of those fake cleaning apps, virus scanners or task managers. My main apps are FaceBook, Instagram and Snapchat.

Any feedback is appreciated, thank you!
[AT&T HTC One (M9)] clsA:
Let the phone settle in

My battery life is very acceptable
[AT&T HTC One (M9)] Jayanyway:
Here I'll show you my screen shots. It's literally just Google Services blowing through my battery.
[AT&T HTC One (M9)] dantegl36:
I'm on the dev version and get decent to great battery life. The data I'm posting below is only 4.6 hours worth but is typical. This is with all radios on, power saver off, emails, a fair amount of pulse usage, youtube, Facebook, some other things and 1hr of talk time.

Your services does seem high.
[AT&T HTC One (M9)] enchanter100:
I believe that you have to let google do it's thing for a while. Eventually it will stop and you resetting the phone that much makes it even worse. This is my opinion and your mileage may very. But stop resetting your phone and give it a week or two and then check and see, you'll probably see that it's not taking much battery anymore.
[One (M7) Q&A, Help & Troubleshooting] OmikronIE:
I've been loving my HTC One M7 for a couple of years now so when my girlfriend's phone bit the bullet I got her one. She's not big on phones so there was no point in paying big bucks for an m8 or m9 so I got her the m7 on ebay. Marked as new and from the uk.

When the phone arrived she had no 4g but I didn't give it much thought as I thought it just might need to be updated and I was going to be rooting it putting on the latest firmware and putting on a custom rom anyway.

I've always loved the Android Revolution mods so I got to work. I checked the cid and thought it was 111 so I grabbed the firmware here - h%%p://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One%2F111%2F I then grabbed Android Revolution 91.1 for all the lollipop goodness. Flashed the firmware, flashed the rom, no issues. But when I booted up I had no 4g only H and with terrible terrible speed. I started digging around and realised my mistake. The phone was s-off and it had supercid - that was the 11111111 I saw. So I figured I had gone with an old firmware going with 111 so I went with the 7.19.401.2 in the 401 folder to get the most recent. Flashed it, no joy. So then I thought it might be a lollipop problem so I went with Android Revolution 84.0 and firmware 6.09.401.5 to have it the exact same as my own HTC One which has great 4g coverage. Flashed the firmware and the rom and I still have no joy. No 4g, and terrible terrible H speed.

I have gone into mobile data settings and they are the exact same as my own phone, i've checked *#*#4636#*#* and they are the same settings. I've popped my sim card into it and it's the same, no 4g, terrible terrible speed H. And I've popped her sim into my phone and it gets perfect 4g.

I've been googling since yesterday but couldn't dig up anything to fix it. Would be over the moon if anyone could tell me a fix or even something to try.

I couple of things:

Does the firmware used matter if the phone has supercid?

Could it be hardware related - i.e. is the phone buggered?
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
have you actually checked in the bootloader that you have an M7_UL (the L stands for LTE / 4G enabled device) it may be that you brought an M7_U (no LTE modem)
[One (M7) Q&A, Help & Troubleshooting] OmikronIE:
That would have been embarrassing...yep M7_UL
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
I wouldn't of thought it would be a hardware problem, can you post the fastboot getvar all of the phone with the issue please without the imei and serial number, just too make sure everything matches up, do not make it s-on at all, it maybe worth changing the CID to HTC__001 (that's 2 underscores) too, super cid has always caused me problems.

also I would stick with the latest firmware, 7.xx.401.x same as what I'm on, also try a different rom, maybe try fuill stock rom which is here: https://www.androidfilehost.com/?fid=95916177934554130 instructions on how to flash it are at the top of the page here: http://xdaforums.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
[One (M7) Q&A, Help & Troubleshooting] OmikronIE:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4T.29.3218.08

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6.09.401.5

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: ##########

(bootloader) imei: ##########

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN071****

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4022mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-6d8a0b9b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

Thanks for the suggestions so far, I'll try changing the cid
[One (M7) Q&A, Help & Troubleshooting] OmikronIE:
Ok changed the cid to HTC__001 and tried the ruu you suggested. Connectivity seems to be worse, no 4g and it's struggling to stay on H. For the record my phone is right beside it on 4g and has 4g everywhere in the house so it's not that the phone is in a bad location or anything.
[One (M7) Q&A, Help & Troubleshooting] OmikronIE:
I hate to bump my own thread but any other suggestions from anyone? I need to know if it's faulty hardware so I can look at sending it back
[G2 Q&A, Help & Troubleshooting] DaINFamousJN:
I just updated my ls980 to lollipop while rooted. I heard that stump root still works but it says im rooted already, but im not. I even downloaded the one click root and that even says im rooted already. I tried rooting again through pc but didnt work. Does anybody know why?