yashsingh1/xdaforums huggingface dataset:
[Sony Xperia P, U, Sola, Go] nosmaster:
i am only giving you my feedback for your ROM the bugs that i personally experianced with you and how i dealt with these bugs to make what i can use as a working rom
[Sony Xperia P, U, Sola, Go] munjeni:
Today I debug kernel for missed boot animatio and found what cause problem... Problem is : framebufer expect RGBA888 logo image but kernel logo.c have no implemented rgb565_to_888 so we need to modify these source and implement them... I got logo working by seting img format inside riogrande mcde but its not good having rgb565 for primary display so definitely logo will be working by implementing rgb565 to 888 part of code...
[Sony Xperia P, U, Sola, Go] jerpelea:
if you fixed it push code here or on gerrit so that we can merged it

br

J

i am debugging a2dp and hope to get it working as it shoudl be soon
[Sony Xperia P, U, Sola, Go] munjeni:
Boot logo fixed :good:

https://github.com/munjeni/android_kernel_xperiago/commit/e035d80e1f98fffe2813d488265bb82fc48ae2ed
[Sony Xperia P, U, Sola, Go] munjeni:
Sorry, my wrong, instead of:

memset32((unsigned int *)bits, widepixel, n << 2);

need to be:

memset32((unsigned int *)bits, widepixel, j << 2);

Its not full fixed (colors is inverted!)... will fix it!
[Sony Xperia P, U, Sola, Go] munjeni:
FXP, did you tried sensors library from here -> https://github.com/sonyxperiadev/DASH

Any progress for keyboard fix? In HTC Aria screen size is 320x480 but in comparation my old HTC Gratia<->Xperia Go, Xperia Go have 4-5mm biger screen than HTC Aria... so maybe Xperia Go screen size have no height 480... just for idea? What you think? Why screen is bigger than HTC but in specification its 320x480?

Do you have idea how we can use kernel sysfs interfaces for diming, blinking...etc leds light:

I see there is some things like "use_pattern"... but not understand how to use them, there is no documentation for these things?

Thanks!
[Sony Xperia P, U, Sola, Go] jerpelea:
we use dash for an long time on other phones

it can not be used in montblanc yet because is missing some sensors

br

J
[Sony Xperia P, U, Sola, Go] munjeni:
Hi, tnx, but what about other 2 question?
[Sony Xperia P, U, Sola, Go] jerpelea:
here is the answer

http://review.cyanogenmod.org/#/c/26126/

you can tweak keyboard from overlay

br

J
[Sony Xperia P, U, Sola, Go] jerpelea:
i have only tried to use trigger and device reboots

blinking lights are low priority

br

J
[Sony Xperia P, U, Sola, Go] munjeni:
The same like me, I allso got device reboot :(... I will try to modify kernel led module and add some standard sysfs interfaces that match names in android lights library... (missing blink, delay_on, delay_off...)

Is android menu "set custom light sensor value" missing because current sensor lib have no these support or it missing because you have no compiled these UI things? I can not see these standard CM9 things for auto light/custom light in android menu that was in every CM9...

Edit:

On first look into kernel source found a lot of strange things... its like kernel have a lot of bugs :(... for example ledtrig-timer.c is enabled in defconfig, compiled, but device_store_atribute mising to store sysfs interfaces for blinking (delay_on and delay_off), its rely strange! Will try to fix these things :(
[Sony Xperia P, U, Sola, Go] jerpelea:
there is no need to do this

blink works

br

J
[Sony Xperia P, U, Sola, Go] jerpelea:
to enable "timer" mode you have to

echo "timer">trigger

then delay_on and delay_off will appear

WARNING!

on devices with dls_pin timer mode is broken and will result an nice kernel panic
[Sony Xperia P, U, Sola, Go] munjeni:
Still X-Go have these (dls_pin ?) so echo timer to triger cause reboot !
[Sony Xperia P, U, Sola, Go] calvin_ng:
Update on latest release 146

Good news

1: No bootloop (Able to boot into Android yay!!!!)

2: Keyboard fixed

3: GPS work - I hope (still testing)

4: receiving and calling works

will report further

Bad news

1: Found signal a little weak

2: Google voice/search did not work (microphone not detected)

3: some how 3G signal quite weak

4: Camera cant read external SD card

5: Cannot import contact from EXT SD card

6: (System cannot read EXT SD card only reconize internal) but Astro can see it

7: Youtube blank screen only audio

-!! Phone not charging... when plug it it shows charging but battery power keep droping... I have revert to old OS... before bat ran out
[Sony Xperia P, U, Sola, Go] munjeni:
Any one know which one apk/framework is for sd card thing? Maybe android settings?

Error on google page for FXP:

I am unable to test version 146 because no permissions to acces the page!
[Sony Xperia P, U, Sola, Go] CiscoX:
Hi.

Maybe it is the fstab file in root / :confused:

EDIT:

Seems to me they have some kind of problems... but i have v.146 i downloaded yesterday.

If you need it, i can try to upload it somewhere else?
[Sony Xperia P, U, Sola, Go] jerpelea:
that fstab MUST be there
[Sony Xperia P, U, Sola, Go] CiscoX:
@ munjeni.

I'm uploading v.146, should be ready soon :)

EDIT:

Link removed as requested. Sorry FXP, I couldn't see where you have wrote at your first post

not to use mirror links

for your uploads :(

I was just trying to help munjeni here.
[Sony Xperia P, U, Sola, Go] munjeni:
FXP, "uploaded" host asking me everytime for premium account so sometimes I need to restart router (change ip address) in order to use his download service in order to download CM release... :mad: ...so my sugestion for every developer here is great Dev-Host service (free premium account is guaranted for every XDA recognised developer account!) ...all "recognised developers" can reguest free premium account here -> http://www.xda-developers.com/andro...cognized-developers-themers-and-contributors/ ...no ads, no stupid waiting, no stupid reguests for premium account, very fast, clean, no slow download... the best server I used ever!!
[Sony Xperia P, U, Sola, Go] OverdiveKill:
is the official rom going to be released any time soon?
[Sony Xperia P, U, Sola, Go] CiscoX:
This ROM is still under development and we need some more testers to test this and report any bugs :)
[Sony Xperia P, U, Sola, Go] jerpelea:
even if we release official cm9/10/11/12 now

it will have same bugs as FXP releases

br

J
[Sony Xperia P, U, Sola, Go] calvin_ng:
im ok with bug as long not a big one hehehe
[Sony Xperia P, U, Sola, Go] OverdiveKill:
Will you release the Rom with no WiFi sleep bug??
[Sony Xperia P, U, Sola, Go] munjeni:
Any one want to give me hint why boot loop is on:

I/Netd (20313): Netd 1.0 starting
E/MAD (20317): thread_setup_socket: Failed to connect to AT Socket: No such
file or directory
E/MAD (20317): dispatch_thread_runner: Connecting to AT socket failed
E/MAD (20317): mad_at_handler_init: Dispatch thread failed to start!
E/MAD (20317): pre_loop_init: Failed to initialize AT handler! Aborting
E/MAD (20317): main: Failed to prepare mainloop!
E/MAD (20317): mad_at_handler_shutdown: Dispatch thread is not running!
E/BandwidthController(20313): runIptablesCmd(): failed /system/bin/iptables -t r
aw -N bw_raw_PREROUTING res=256
D/MDnsDS (20313): MDnsSdListener::Hander starting up
D/MDnsDS (20313): MDnsSdListener starting to monitor
D/MDnsDS (20313): Going to poll with pollCount 1
E/Netd (20313): Unable to start MDnsSdListener (Invalid argument)
E/SocketListener(20313): Obtaining file descriptor socket 'mdns' failed: Invalid
argument
E/NetdConnector( 5592): Communications error: java.io.IOException: No such file
or directory
E/NetdConnector( 5592): Error in NativeDaemonConnector: java.io.IOException: No
such file or directory

No such file or directory... what I need to do, thanks!
[Sony Xperia P, U, Sola, Go] jerpelea:
ignore it for now, there is no support !
[Sony Xperia P, U, Sola, Go] munjeni:
Sorry for being off topic but what I trying from now is booting gerit AOSP rom that I have now compiled but have boot loop on "android starting" mesage on screen after "optimising all apps" message... still boot loop is on these message from previous post and I am unable to solve. Found missing "/dev/socket/at_core" but after executing command "/system/bin/at_core" got error "cannot locate '_ZN7android1ToneGeneratorC1Eifb'" ...have no idea how to solve missing library (tone generator lib is in ste_omxcomponents folder linked to lib dir too)... do you have idea what is missing? Thanks!
[Sony Xperia P, U, Sola, Go] jerpelea:
you are missing my audio patches :)

Br

J
[Sony Xperia P, U, Sola, Go] munjeni:
what exactly... you mean "lotus: duplicate blobs to satisfy audio dependency"? Please give me direct link to patchset, Thanks!

Still problem remain when I execute at_core or admsrv:

libste_adm.so:

.text:000039B8 BLX _ZN7android13ToneGeneratorC1Eifb ; android::ToneGenerator::ToneGenerator(int,float,bool)

Is something missing in libhardware legacy? Or framework side? Thanks!

Edit:

Found ansfer by self:

stock libs:

But in AOSP libs, instead of string _ZN7android13ToneGeneratorC1Eifb there is string _ZN7android13ToneGeneratorC1E19audio_stream_type_tfb... so I need to patch these 3 libs to get these working :( If you have better idea please let me know... just want to find how AOSP working in Xperia!
[Sony Xperia P, U, Sola, Go] jerpelea:
https://github.com/CyanogenMod/andr...mmit/66155a8b94ae169923975c5b6d7d259bacc13533
[Sony Xperia P, U, Sola, Go] munjeni:
Thanks, but I think current problem for boot loop will not be fixed with these commit... I found what cause problem! Problem is many diferencies between frameworks in AOSP JB and in CM9 ICS, for example in ToneGenerator.cpp (in JB definition is "audio_stream_type_t" but in ICS "int")...etc, so "prebuilt" Sony libraries is not "all" compatible with JB :( ...I not understand why Sony can not give us "hardware" libraries sorces public... this phone without these things is not "user friendly" for development. For example we need audio libs, libhardware, liblights, sensors...etc. Maybe I am wrong... source code is opened public?
[Sony Xperia P, U, Sola, Go] calvin_ng:
perhaps we can request from talk.sonymobile.com or their developer support website see if they can help us out... since sony openly state they support open community and support AOSP
[Sony Xperia P, U, Sola, Go] munjeni:
Yes, you are right, we have a lot of missing "opened public" things needed for develpment on AOSP or any other... I am not happy now, still I am unable to continue boot process on JellyBean Gerit AOSP rom (but got screen message "optimising apps...etc but boot loop on...) because missing compatible "at_core" libs that is needed for these build, still "prebuilt" ste_* components is not compatible with these build. :( I have no idea where to get these source code... coplete modifuing android framework/av* media things just for libste_adm have no sense I think, Sony I think need to open these libraries public for developers! More friendly things for us is more friendly for Sony popularuty! Is not? :)
[Sony Xperia P, U, Sola, Go] KeiranFTW:
Better to wait for jellybean prebuilts from Sony stock jellybean.
[Sony Xperia P, U, Sola, Go] munjeni:
These logic mean: if his JellyBean have bugs we will have bugs too! But why? Why not simple open these libs public so 1000000000000 developers can contribute to his source code and get something better for whole comunity! Is not better idea? I no want to wait, I want CM Jelly Bean and not Sony JB :) ...I not like prebuilts too. Sorry for being off topic!
[Sony Xperia P, U, Sola, Go] KeiranFTW:
They can't open source all stuff - if they did other manufacturers could steal their work to use on their phones. Even nexus devices have some proprietary libraries needed when building.

They open-source what they have to, and sometimes more. Look at DASH for example.

So you will have to wait for JB prebuilts, or either write it all yourself, or try and get some things from igloo to work.

The ste stuff doesn't belong to Sony either, it's ST-Ericsson proprietary and obviously at this point they don't want to share it.
[Sony Xperia P, U, Sola, Go] jerpelea:
here i think that i should speak

Sony is using ST-Ericsson code wich is closed source so if you want to create an petition you can start writing it to ST-Ericsson

if you look on igloo you will see that even there (for montblanc board) igloo has only blobs for ST -Erricson hals

BR

J
[Sony Xperia P, U, Sola, Go] calvin_ng:
Why not try contacting developer@Sony lets see if they can help out since Sony has jb on next line up
[Sony Xperia P, U, Sola, Go] munjeni:
I am unable to register to Sony forum... geting message on site "system error..."
[Sony Xperia P, U, Sola, Go] dimon2242:
Register with Google account?
[Sony Xperia P, U, Sola, Go] munjeni:
Hallo, whats going on Cyanogenmod git, I can not see any source for X-go... is development stoped and source code deleted for Xperia Sola, Go...etc?
[Sony Xperia P, U, Sola, Go] jerpelea:
https://github.com/CyanogenMod/android_device_sony_lotus
[Sony Xperia P, U, Sola, Go] munjeni:
Strange, its not on index page of cyanogenmod, only direct link can access xperia...
[Sony Xperia P, U, Sola, Go] jerpelea:
there are 660 repos and not all can be displyed on first page

now i pushed new changed and repos are in front
[Sony Xperia P, U, Sola, Go] Androboss:
I have already used Flashtool with stock ICS, then recovery, then try and install zip FXP147 but i get error status 7, build prop is set to ST27a and my device is ST27i guess that is why it wont work.

Can you please state in first topic which version this is for so people dont waste time.
[Sony Xperia P, U, Sola, Go] nosmaster:
follow munjenis post to me on the second page
[Sony Xperia P, U, Sola, Go] Androboss:
I did read it.

ADB does not work in the recovery that is in FXP release.

Guess you did not read what i wrote.
[Sony Xperia P, U, Sola, Go] calvin_ng:
please follow the thread and read it all dont comment when you did not read all

ststus 7 when you flash wrong cwm

---------update------------

No status 7 during CWM

No bootloop but stuck at CM9 boot animation...

unable to proceed further...

--- I did factory wipe / cache wipe / dalvik wipe
[Sony Xperia P, U, Sola, Go] munjeni:
I had problem for downloading from uploaded.net rom FXP146 and have problem too for FXP147 so I am unable to download and test FXP147... every time site asking me for premium account or fail to start doownload...etc (tried 2 browsers and no want to waste time with third one) still these site have a lot of dirty html and java things so site pages not working propertly and have a lot of js errors... see picture http://img20.imageshack.us/img20/4218/20121118104323.jpg I could not see button for download, uploaded.net is realy an s***

About ro.build.product st27a... maybe there is a mistake? I know st27a is for Xperia Pepper so maybe devs had a mistake and instead of Lotus he made rom for Pepper?
[Sony Xperia P, U, Sola, Go] OverdiveKill:
FXP 147 is still not intended for daily use?
[Sony Xperia P, U, Sola, Go] calvin_ng:
It can be used it depends what your daily habits are... but It still stcuk in CM9 boot screen... any idea to get it booting??? I suspect it is kernel...
[Sony Xperia P, U, Sola, Go] munjeni:
Mirror links? :rolleyes:

edit:

oh my god, after one hour of refreshing uploaded.net page, cleaning temp internet files, restarting browser, restarting router to change ip address... download is started, wauuuu:crying:

edit:

Rom fail to boot, logcat have a lot of errors and warnings... hw lights library can not be used for version 147 because kernel need fix for triger "timer" because writing to triger cause device reboot!!! External_sd allso fail...etc! I will try to fix these kernel triger module for lights.

Hope next version will be easy for download? Here is logcat!
[Sony Xperia P, U, Sola, Go] munjeni:
FXP, need help... do you know what cause crash...? I think "mod_timer" ...do you have idea?
[Sony Xperia P, U, Sola, Go] jerpelea:
i am already working on it

br

J
[Sony Xperia P, U, Sola, Go] teocomi:
I personally had problems with 144 and 145. FXP 146 I could install easily, but again now with 147 I get either booting loops or status error..

P.S.

What do you mean with "- fastboot flash boot boot.img (from cm10 zip)" I have always used the "boot.img" contained in the release's .zip file..

Btw thanks for the great job!
[Sony Xperia P, U, Sola, Go] Androboss:
There is no Lotus release of CM10, it is just great when people just copy paste it all without even checking if it would work in the end.
[Sony Xperia P, U, Sola, Go] munjeni:
Ok, good! Did you tried http://www.malideveloper.com/develo...n-source-mali-gpus-android-gralloc-module.php
[Sony Xperia P, U, Sola, Go] jerpelea:
finaly i have working notification lights
[Sony Xperia P, U, Sola, Go] munjeni:
Please give us another miror instead of uploaded.net
[Sony Xperia P, U, Sola, Go] angelerikz:
FXP148 for lotus is not yet available for download at uploaded.net
[Sony Xperia P, U, Sola, Go] munjeni:
Ok, I understand, but I can use rapidgator without any problem, but latest release uploaded to rapidgator is 147... do you have plan to upload version 148 to rapidgator or we need to wait mirored links?
[Sony Xperia P, U, Sola, Go] teocomi:
Flashed 148, but still having boot loop issue.. Will try again with the mirror release!

Thanks for the effort and the quick release anyway!
[Sony Xperia P, U, Sola, Go] munjeni:
Adb not working in v148 so unable to see whats happen
[Sony Xperia P, U, Sola, Go] jerpelea:
replace in build.prop (in zip) mtp with adb
[Sony Xperia P, U, Sola, Go] munjeni:
W/MountService( 4154): getVolumeState(/mnt/external_sd): Unknown volume

E/AndroidRuntime( 4154): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread

it was in v147 too !
[Sony Xperia P, U, Sola, Go] munjeni:
I'm sure 149 will boot :) ...You can replace font in recovery with 10x18 because current font is very big for xperia go! Thanks for your hard work!
[Sony Xperia P, U, Sola, Go] jerpelea:
changed on request for FXP148a
[Sony Xperia P, U, Sola, Go] jerpelea:
uploaded 148a
[Atrix 4G Q&A, Help & Troubleshooting] sk8rdude:
Hello Guys..

Recently got hold of a pre-rooted atrix from a relative who upgraded his phone.

Due to less time on hand, i just couldnt get all the details about it, and now i am in a fix..

Info:

Its an ATnT Atrix 4g.

System Ver: 4.5.91 / Android: 2.3.4

Current ROM: Alien #2

Its already rooted and bootloader is unlocked as well. CWM Recovery is installed too (i asked these parts specifically)

I have an external SD card as well.

The phone already had few contacts saved with one google account. I created mine and saved few of my own.

I avoided saving contacts which were common with my relative.

Questions:

1) How do i merge contacts from both the accounts, and then delete one a/c?

2) Which is the best s/w or app to backup all the contacts and sms ?

3) How to find out which CWM has been installed ?

4) No idea about fastboot thing being installed or not.. how do i find out ?

What's its exact need/function ?

I apologize in advance for asking so many questions.. i did tried to search beforehand.

And i did tried google as well, but wherever i tried reading, they seemed to be a level ahead of me and i was left all confused. I been busy and out of station a lot offlate as well.. hence posting and asking here as my relative advised me. Just need to get it configured asap and try it out properly.
[Nexus S Q&A, Help & Troubleshooting] xdatastic:
Yesterday I flashed my i9023 back to Gingerbread 2.3.6\GRK39F (just for fun) using the official Google factory image from here:

https://developers.google.com/android/nexus/images#soju

I notice that the NFC no longer works and gives the error message 'an error has occurred' (or something to that effect) when trying to activate it.

Has anyone else noticed this? My NFC works fine on all the other images so my hardware is good, and it used to work back in the old days.
[Nexus S Q&A, Help & Troubleshooting] ozone89:
Have you wiped it properly beforehand?

If not, there's a guide in the General section
[Nexus S Q&A, Help & Troubleshooting] mutantlx:
If I recall it was a bug on 2.3.6 regarding NFC. Hence the update to 2.3.7.
[Nexus S Q&A, Help & Troubleshooting] xdatastic:
yes, i unlocked bootloader via fastboot which wiped the device. also the factory images flash-all.sh script wipes by default.
[Nexus S Q&A, Help & Troubleshooting] xdatastic:
2.3.7 was for the 4g nexus only.

anyone feel like flashing back to GB to reminisce the good old days and see if nfc works? :)
[Nexus S Q&A, Help & Troubleshooting] mutantlx:
I stand corrected :thumbup:

I had oxygen on my nexus the other day and all was fine when I disabled NFC.
[Raspberry Pi General] trevd:
Hi Folks

Recently I helped Adam Outler get adb compiled for his Pi This was not as simpe as it first sounds because as we learnt adb on the host is subtlety different from the one compiled for the target and the AOSP source tree does not support compiling androids host tools for arm out of the box.

However You can add the armv6l host support by creating the file

<aosp source root>/build/core/combo/HOST_linux-armv6l.mk

The contents of which should look something like this

# Configuration for builds hosted on linux-armv6l.

# $(1): The file to check
define get-file-size
stat --format "%s" "$(1)" | tr -d '\n'
endef

HOST_SDK_TOOLCHAIN_PREFIX :=
ifneq (,$(strip $(wildcard $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc)))
HOST_CC := $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc
HOST_CXX := $(HOST_SDK_TOOLCHAIN_PREFIX)/g++
HOST_AR := $(HOST_SDK_TOOLCHAIN_PREFIX)/ar
endif # $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc exists

HOST_GLOBAL_CFLAGS += -fPIC
HOST_GLOBAL_CFLAGS += -include $(call select-android-config-h,linux-x86)
HOST_GLOBAL_CFLAGS += -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0
HOST_NO_UNDEFINED_LDFLAGS := -Wl,--no-undefined

You can now use the native pi toolchain to build with the aosp sources, at the very least you'll be able to compile the host tools such as fastboot , adb natively on the Pi. Whether you'll want to go about compiling a full android build using the Pi and whether that is even remotely sensible is a discussion for another day! :laugh:
[Raspberry Pi General] fewesttwo:
Hey, thanks for your work on this. Sensible or not, it would be pretty cool to run an AOSP or even a CM build on your phone that was compiled on your Pi.

I tried compiling Boot2Gecko for my SGS2 on my Pi as well, but that kept dying about 6 hours into the build :(.

I got really lost (just learning all this stuff now), but learning it all while building a project you really like would be far more interesting that learning it while building "nano" or "Vim".
[Raspberry Pi General] trevd:
Yes or compile on the Pi for the Pi, If you want to try do that there's the beiginings of the other side, i.e armv6 target files on my github, It actually targets armv5te because that is already present as a valid target in the AOSP build system, a throwback to pre gingerbread and the HTC Dream ( G1 ) etc.

Thinking about it though, The build system may need a little more adding as I think only x86 based cross compilers will be currently selected for target compilation. I'm yet to get my Pi, there's currently a 6 week lead time on them and I'm thinking about holding out for the 512MB version. Until then it's QEmuPi for me!

The Android build system is pretty forgiving and will let you compile things piece-meal which is good because I don't think it would make it all the way to the end in one go no matter how many hours you give it.
[Raspberry Pi General] AdamOutler:
Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. :). I'm pretty sure its a mailing list.
[Raspberry Pi General] pulser_g2:
Indeed, it's at https://groups.google.com/forum/?fromgroups=#!forum/android-contrib