yashsingh1/xdaforums huggingface dataset:
[Xperia Play Q&A, Help & Troubleshooting] :
Hi, it had an unlocked bootloader, was rooted, running Stock ICS Xperia Play 4.1.B.0.587 Final rom.

Ive tried a few things over the last few hours with no luck, i tried flashing different firmware, i tried sony pc companion, managed to update it at one point but nothing has seemed to work...

before the phone stopped working, recently ive had to press the power / home button a few times to wake the screen, right now the phone will charge and still orange / green light...

when i power on the phone it will vibrate once and nothing will happen, android wont boot no matter what i do

Any help appreciated
[Xperia Play Q&A, Help & Troubleshooting] Xperia Player:
Try pulling the battery, try flashing again with flashtool using different USB ports, make sure your battery is a good 50% charged before attempting the flash process.
[Xperia Play Q&A, Help & Troubleshooting] creative_md:
You updated it on unlock bl so flashtool won't work you hav two options. Relock bl then flash via flashtool or apply patch of .ta file
[Xperia Play Q&A, Help & Troubleshooting] :
thanks for your help, ive tried different usb ports, i have relocked the bootloader and flashed afterwards, but still nothing, ive got a feeling that the patch might work, could you give me more help regarding how to do that.... (fingers crossed)
[Xperia Play Q&A, Help & Troubleshooting] creative_md:
follow this http://xdaforums.com/showthread.php?t=1126354
[HTC One X] SammyK300:
Hi guys, need some help, rooted and installed slimbean just 2 days ago and everything was going great.

Pulled my phone out of my pocket today and the screen wont come on. Captive buttons come on and off with each press of the power button.

Holding down the power button reboots phone (captive butons flash and phone vibrates) but still same problem and tried getting into bootloader but not 100% sure that its going into it as same symptoms as before.

Tried hooking up to a few computers at work and it just says USB drivers failed to install as problem with USB device.

LED still lights up for charging.

Any ideas?

Thanks in advance for your help.
[HTC One X] iang265:
How long was it in your pocket for? Is it possible the battery has run out? If so then there is always the possibility the juice running out coincided with an error. It might mean you need to try the batch files to charge your phone?
[HTC One X] SammyK300:
Last time i looked at the phone about 15min earlier i had about 25%

Has been on charge for about 30 min and now i only get the LED, captive don't light up, doesn't seem to reset when holding the power button.
[myTouch 4G Q&A, Help & Troubleshooting] demoncamber:
I want to compare settings with mine could someone upload me the files found in the sys/devices/system/cpu/cpu0/cpufreq/ folder?

THANK YOU!!
[myTouch 4G Q&A, Help & Troubleshooting] wizardwiz:
I will bundle my files in a zip/rar file and upload it for you later on today.

BTW, as far as I know, these files are kernel bounded so you can't change them, right?
[myTouch 4G Q&A, Help & Troubleshooting] demoncamber:
Thanks, greatly appreciated, I'm using oc/uv beater to change settings, i just want to compare vdd and a few other settings with my defaults.
[Miscellaneous Android Development] einsteinecker:
Changelog

Latest Kernel:

March 14 2013

ReRun New Compile

This kernel was compiled differently than previous kernels, intended to join together the incompatible drivers with the rest of the drivers. This fixed several problems. Read here for more info.​

-

November 23, 2012

ReRun kernel build 119

This kernel was restarted from the beginning, and slowly configured to the point where I found a solution to the "connect charger" error on boot. Basically, the kernel source had conflicting power settings combined from the HD2 and Tsunagi sources, and I simply removed the HD2 battery settings and provided a new working source code for the battery. I expect to use this as a base as I further eliminate the invalid .32 codes and replace it with .35 sources.​

-

einstein 4x1 (NOTE: read any "readme.txt" files for instructions!!)

-Now, phone will no longer reboot when booting into android. You must make sure your battery level is over 26% in order to avoid this Reboot of Death bug, as it seems like the current build will reset if Android is in a mode where it will warn you to connect your charger. Perhaps we can change Android's low battery notification?

-NVRAM now pointed to /system/etc/wifi/, be sure to root copy the nvram.txt file into the new location.

-(for my modified Gingerbread build) attached are the correct key layouts for the Fathom hardware keyboard (thanks to www2287​

Extreme Battery 003

-Re-started kernel development to ensure junk drivers were no longer included. This led to working Wifi, partial bluetooth, fully working headphone support, accelerometer, and as before, no immense power drain on standby. Overnight standby now a reality with Kernel 003!​

Extreme Battery 002

Fixes:

-Wifi for Froyo, Bluetooth for Gingerbread

-Accelerometer works for Gingerbread only

-Headphones now work without fail

-Need more feedback regarding resetting while phone is on or off​

Extreme Battery 001

Features:

-More CPU governors

-Overclock enabled (use at your own risk!)

-Extreme battery saving (need confirmation, my battery only dropped 2% overnight!)

Working:

-Main speaker

-Phone earpiece

-d-pad now aligned properly

-No more torn screen on the left side!

-Real power-down! Power button is the task manager button beside the camera button. Press this to turn your phone on or off.

Not working:

-Same as before, no outgoing SMS

-Wifi is dead :silly:

-Camera not working

-Never tried GPS...

-When headphones are plugged in, sound dies globally in Android.​
[Miscellaneous Android Development] einsteinecker:
Frequently Asked Questions

Where's my microSD card?

It seems strange, but this way worked for me: before you boot into Android, remove the sd card from your phone, then insert it, and then immediately boot into Android. If you did not do this when booting Android for the first time, do this method.

I'm low on storage space.

In "startup.txt", change "data_size=256" to "data_size=512" for 512MB of storage space. If you want more, change 512 to 1024 or 2048 for 1GB / 2GB respectively. Make sure you have that much free space on your MicroSD before you continue!

Can't start Froyo 2.2?

When you see the system process error, immediately press the side button beside the camera, then choose wait, then hold side button, then select power off, and the phone should look like it's booting again, and it should go into Froyo. If it doesn't, repeat again.

Can't boot into Gingerbread 2.3?

Due to a fault in ajeet's battery driver, the OS does not know what the battery life is at boot, and it thinks the battery is dead. Solution? Just make sure you have at least 70% or higher battery life when you boot into Android. I will try to focus on this, but as of the moment, I have not had much success in porting drivers into the kernel, as it is a rather complicated process and it has to be done in a way that will not break the wifi again. (This issue has been fixed in ReRun kernel build 119)
[Miscellaneous Android Development] einsteinecker:
Reserved
[Miscellaneous Android Development] pizzaboy192:
Awesome that we have someone working on this again. Slightly curious how hard it would be to port this work over to OpenWebOS... But I'll love to see where Android goes. I'd try using it if the CDMA radio worked.
[Miscellaneous Android Development] einsteinecker:
I'm optimistic CDMA would work, that unfortunately might need to have the Android OS edited to support dual mode CDMA/GSM. A nice place to start would be the Android builds for the Touch Pro2.
[Miscellaneous Android Development] pizzaboy192:
We should also see what other Android-only devices used the same modems. The Droid series usually were world devices, as were a few others (none off the top of my head, but I bet they're pretty easy to find)

Worst case scenario would be to compile two different Android versions that are either CDMA only or GSM only.

I've got 3 Fathoms to test on, and would be more than willing to sell my unlocked one to someone who could use it better than I could (it's currently de-activated and I don't have a GSM SIM to test.
[Miscellaneous Android Development] Giorgi-geo:
nice! thanks for your work einsteinecker
[Miscellaneous Android Development] Giorgi-geo:
so here's my problem. i did everything as said. HTC logo comes on and that's it. i waited for 40+ minutes for it to load but nothing

edit: never mind. On the third try it loaded correctly :)

---------- Post added at 09:38 PM ---------- Previous post was at 09:00 PM ----------

love you. please fix wi-fi soon )

---------- Post added at 09:44 PM ---------- Previous post was at 09:38 PM ----------

i was using 2.3.1 android before this. now i installed 2.2 and the difference in performance is huge. 2.2 is much faster and smoother on our device. can you tell me what is the key difference between 2.3.1 and 2.2? if there is none I think it will be better to have 2.2

forget this too. looks like both build work better with your help )
[Miscellaneous Android Development] Giorgi-geo:
Also. when in android, and i connect USB and transfer some files onto sdcard. they dont show up in file manager until reboot, and sometimes they just disappear. this is happening since first ajeet build - not a new problem, but maybe you could look into it.

---------- Post added at 02:47 AM ---------- Previous post was at 02:36 AM ----------

bluetooth also does not work )
[Miscellaneous Android Development] einsteinecker:
Sorry folks, I meant to update yesterday but I had a mind crushing headache :(

I recall most Droids from Motorola have the OMAP cpu, so I'm not sure if using the code for that would work on our Qualcomm stuff (I believe LG used a Qualcomm reference guide for the Fathom). I figured checking Qualcomm's sources first is a good try.

I've been interested in something. How is android on the newer updates? What I mean is that, I'm still running stock V4 Windows Mobile ROM on my Fathom, and there is no performance lock like on the HTC HD2 (full 1Ghz on battery). Does the V5 or V7 WM Roms have this too?

One main difference I see between 2.2 and 2.3, is that 2.3 rotates the screen immediately after you slide out the keyboard. 2.2 will only rotate once you open a program.

If you read the readme text file inside the 2.2 Android build, you'll see it's a problem of the OS:

"- USB Mass Storage (You can copy files from PC to PC. But Android apps cannot see the copied files in the phone before rebooting.)"

I think that is because we run Android from our SD card.

Thanks for the feedback. I was going to upload the headphone fix yesterday, but maybe I'll try that bluetooth fix too.
[Miscellaneous Android Development] pizzaboy192:
I am not sure what the differences between the OMAP refrence and the Qualcomm refrence designs are. I know the Fathom is a 1ghz Snapdragon, but not sure what else it has in it.

Also, what do you mean by performance lock? I run my own ROM (V6) and it seems to run well. I don't do OC, but I have successfully underclocked the device to 215mhz (somewhere around there) as a test and it was stable. Eeked almost two weeks of battery out of a test device that way.
[Miscellaneous Android Development] Giorgi-geo:
maybe you could fix wi-fi too? it was working before, so if you could compare the code you could probably fix it fast.

---------- Post added at 12:42 PM ---------- Previous post was at 12:19 PM ----------

one more thing. in android it only shows 165mb ram

---------- Post added at 12:54 PM ---------- Previous post was at 12:42 PM ----------

I think this just happened to me. every time i load android it goes to unlock screen and then turns off. i always turned android off from its own menu so i dont know why it happened. there has to be a way to fix this, help please?

---------- Post added at 01:46 PM ---------- Previous post was at 12:54 PM ----------

after 5 tries, i connected phone with charger and on the second try it turned on :D
[Miscellaneous Android Development] einsteinecker:
Hi folks, after my previous build work for headphones and not Bluetooth, I tried fixing Bluetooth but now the headphone port is wonky :silly:

While that was happening, I found out why Wifi wasn't working. Now, on 2.3 Gingerbread Wifi doesn't work (probably firmware problem), but in 2.2 Froyo it does work, but can't find any networks :(

That's when I was trying to fix things on the Android side (not the kernel) when I apparently got one thing to partially work:

I hope you noticed the 3G icon on the top, yes it's very close to working, the only problem I've got is making the phone realize that there is a sim in there (and the outgoing number to dial). Now, 2.3 Gingerbread can see the sim, so I'm going to try that, but if this works, I think we're in for a heck of a ride :D

Once I have both headphone and Bluetooth support stabilized, I will upload that. The 3G and Wifi fixes involve the Android OS itself, so that means I have to uploaded the OS or give instructions how to patch them in yourself.

Well I certainly won't rule anything out. Right now any thing is a good thing to test, who knows, maybe the Droid actually has what I'm looking for :cowboy:

Performance lock is like this: when I had the HD2, while on battery (no AC plugged in) the phone will have only a maximum speed of 768Mhz. My Fathom does not have this, it is a max 1Ghz on battery and on AC. What I'm wondering is, maybe LG's V5/V6/V7 updates changed something, I'm not sure. I sure don't want to risk my only phone either, and there's more: what if all this time LG's updates also updated the phone baseband. So while I'm porting Android to our phones, maybe my updates won't work with the old V4 I'm running. There certainly is a lot of things to consider when doing this stuff :silly:

I think there might be a way to fix this, unfortunately I have had little succes porting drivers over to my kernel. It is one of the reasons why I can't get the camera to work yet, porting drivers is not as simple as copying and pasting drivers like in windows mobile.

But I think it could work, you see, my idea was to tell Android that there's a reset button onboard the phone (the one beside the charging port). LG has the code for this, which I was able to see, but haven't been able to get working yet.

Edit: Wifi is still dead on 2.3 Gingerbread, but I fixed the Accelerometer :victory:

Couldn't test Froyo because I broke the Android build, will redo and continue further tests
[Miscellaneous Android Development] pizzaboy192:
Awesome work! I'll run some tests on my end with the CDMA half if you'd like and report back to see what is and isn't working connectivity wise there.

As for the WiFi half: is it getting an IP address? Can you check the DNS settings to make sure they are being set properly?

As for the performance lock: none that I know of.

And as for the question about baseband: No baseband differences between ROM versions. They're purely a WinMO flash, and not a BaseBand flash. If you'd like, I can run tests on all 3 OEM versions of the ROM though, as I have 3 unused Fathoms, all on different ROM versions currently. I've even tried cooking a WinMo ROM that autoboots into Android (almost works, tempted to just put a HaRET shortcut in startup and strip out all WinMO core programs.
[Miscellaneous Android Development] einsteinecker:
Froyo doesn't like my kernel anymore, even tried a different SD card and it still has a system crash on boot. I guess it's time to work on a new OS :crying:

It's just scanning, it won't even find the network :(

Oh, that's what I wanted to know, if the LG updates include a radio update. I'm highly interested in knowing if there will be better performance in Android if they updated the radio.
[Miscellaneous Android Development] pizzaboy192:
We could also see what other devices used the same radio chip. I know that plenty of them are out there, it's just a matter of finding one that will provide an updated baseband and see how badly it screws up the phone (since we don't have the OEM baseband, doing that would probably brick any device you modded, if it went wrong)

How are you doing your work? any possibility of throwing it on some place like github so that people like me can try out changes and put our own in to help out? I have a test fleet just sitting doing nothing since I can't get much more out of Windows Mobile and cooking ROMs has gotten rather repetitive.
[Miscellaneous Android Development] einsteinecker:
The kernel source is in the first post :D That's all I'm doing now, I get discouraged when I see the steps I have to take to make the Android OS, neither ajeet or www27 uploaded that and it's going to be a lot to download (I have limited bandwidth) What I've been doing is modifying Android while it's running (root access), and that's how I applied the accelerometer and that 3G thing.

Tomorrow I will upload the latest fix, which includes:

-bluetooth support (paired with headset and able to receive files)

-headphone support fixed

-how-to for the accelerometer (I will add a game so you can test it :))

I'm currently prioritizing 3 things: why the SD card doesn't always mount on boot, charging the phone while using Android, and why my kernel doesn't like Froyo and the fixes that used to work.
[Miscellaneous Android Development] Giorgi-geo:
what's wrong with charging? i dont see any problems:confused:
[Miscellaneous Android Development] pizzaboy192:
Random question: any way to get the Android main to boot off the internal flash? if so, I could build "ROMs" that boot WinMo and immediately start HaRET and handoff to Android. I tried earlier, but ended up with a failed boot every time.
[Miscellaneous Android Development] www2287:
hm windows button is working for me (as android "home"). here is my current kernel-side layout. our space button uses 2 keys (left side and right side); "sound" button (in top of dpad) will work as MENU. change your kernel layout to this for new releases:

file arch/arm/mach-msm/lgdevices.c

static unsigned short pp2106_keycode[PP2106_KEYPAD_ROW][PP2106_KEYPAD_COL] = {
{KEY_UNKNOWN, KEY_1, KEY_2, KEY_3, KEY_4, KEY_5, KEY_6, KEY_7},
{KEY_8, KEY_9, KEY_0, KEY_UNKNOWN,KEY_Q, KEY_W, KEY_E, KEY_R},
{KEY_T, KEY_Y, KEY_U, KEY_I, KEY_O, KEY_P, KEY_LEFTSHIFT, KEY_A},
{KEY_S, KEY_D, KEY_F, KEY_G, KEY_H, KEY_J, KEY_K, KEY_L},
{KEY_BACKSPACE, KEY_LEFTALT, KEY_Z, KEY_X, KEY_C, KEY_V, KEY_SPACE, KEY_BACK},
{KEY_SPACE, KEY_B, KEY_N, KEY_M, KEY_MENU, KEY_UP, KEY_DOWN, KEY_BACK},
{KEY_RIGHT, KEY_LEFT, KEY_ENTER, KEY_K, KEY_UNKNOWN, KEY_HOME, KEY_MENU, KEY_MENU},
{KEY_ENTER, KEY_VOLUMEUP,KEY_VOLUMEDOWN,KEY_END, KEY_UNKNOWN, KEY_BACK, KEY_MENU, KEY_END},};
[Miscellaneous Android Development] pizzaboy192:
www2287,

I have an issue with the ROM you posted. I cannot install any apps into this build. Installing onto Internal storage causes it to go back to the CyanogenMod loading screen and then a fresh home screen. Installing onto external storage brings me a "Application was NOT installed" style error.

Is this common, or is it something that is specific to my system? (I'm using a freshly formatted and empty Class 6 card 8GB.)
[Miscellaneous Android Development] einsteinecker:
Thanks, I noticed in the previous kernels that the right spacebar didn't work, now it works :D

That's weird. I'm able to install apps, and have already installed several. I'm wondering, is your windows key working for you? Must be something we're doing, or maybe this is specific to the Fathom version of the phone. My phone is running V4 software, which version are you using?
[Miscellaneous Android Development] www2287:
my software is V5.

i have found the problem: this bug appeared to me when i wiped data.img. will try to resolve the problem.

and i'm able to install apps too => try to kill data.img

good news: i found our libsensors sources, so, we can add proximity sensor support to this lib in future
[Miscellaneous Android Development] pizzaboy192:
My Windows key is not working. I'll try some stuff to my card and see what happens.

My phone is running my V6 ROM that I have posted on my site, but it's a custom build for my own purposes. I'll test it on a V7 ROM later today, along with a V5 ROM to see what happens on each. (Since I have 3 phones to test on)
[Miscellaneous Android Development] www2287:
this is a known issue. i will fix it closer to weekend
[Miscellaneous Android Development] einsteinecker:
I must be the only one running V4 :p

I forgot to mention headphones did not work because it was missing some files, can you add them? (attached)

These two files go into /system/etc:

AdieHWCodecSetting.csv

AudioBTID.csv

This file goes into /system/lib:

libhtc_acoustic.so
[Miscellaneous Android Development] pizzaboy192:
can we have the CDMA files from a few pages back integrated as well? I'd be able to play with settings to try and get CDMA working before I switch over to a new phone.
[Miscellaneous Android Development] www2287:
will add latest libs from htc desire cyanogenmdo

but on ajeet kernel it was work without these libs very well.

---------- Post added at 08:37 PM ---------- Previous post was at 08:35 PM ----------

worldphone feature is enabled in cm configs, but it is not working cuz we use HTC gsm ril. there is no lib with full support of our radio
[Miscellaneous Android Development] einsteinecker:
Because ajeet was using 2.6.32, with headset driver "board-swift-headset.c". In .35 that driver only detects if a headset is plugged in, and sound won't work unless I enable HTC acoustic. I tried compiling without "board-swift-headset" and headpones won't work at all.

I looked in Swift kernel 2.6.35 and it does not have board-swift-headset.c, that means the headset driver changed for .35 but I don't know which one. So for now we use HTC acoustic :silly:
[Miscellaneous Android Development] nalanickal:
* Any body tested CDMA ?
[Miscellaneous Android Development] pizzaboy192:
As of right now, CDMA does not seem to function. I honestly cannot get the phone half to function at all. WiFi does work.
[Miscellaneous Android Development] www2287:
ok, will add :)
[Miscellaneous Android Development] pizzaboy192:
I copied over the CDMA files from a few pages back, and was able to get the GSM modem to turn on. I do not have an active GSM SIM card, so I don't know how well it will work. I'll also be testing GPS and see if Android will work as a base for a handheld GPS unit.
[Miscellaneous Android Development] einsteinecker:
I have some ROMs from developers that I can try, give me about 5 days, and I'll see what I can do.
[Miscellaneous Android Development] Giorgi-geo:
Hey guys. Any update?
[Miscellaneous Android Development] einsteinecker:
Hi, have you tried ReRun kernel? Other than that, I'm keeping my health in check, and I'm still taking care of my hard drives, and unfortunately, that will need to finish before I can move my Ubuntu installation to a fresh hard drive, that Ubuntu drive is now automatically re-allocating bad sectors and I do not want to lose my kernel work by continuing to use that drive.

I have also been trying to figure out the current problems of the ReRun kernel, and I believe I can utilize my battery saving config from my very first kernel (cyanogenmod still drains battery), as well as the USB problem, I have an idea, but I need to access my Ubuntu drive so that will have to wait. :(

I'm still in the fight though, and I want to see it through.
[Miscellaneous Android Development] Giorgi-geo:
yes i tried it and it's great. btw i wanted to ask you, could you somehow include gapps in these builds in the future?
[Miscellaneous Android Development] Giorgi-geo:
which one is the best for our phone? https://play.google.com/store/search?q=mx+player&c=apps
[Miscellaneous Android Development] einsteinecker:
I wonder why ajeet removed those apps... I'll remember to add them in the next release, but if you want them, try the link here.

I use MX player ArmV7 NEON. That video player was able to play some of my 720p videos :D