[GT-S5282] CM 10.1 Bugs, Disscussion, Questions, - Samsung Galaxy Star

Orginally, this was the thread for the rom, And this was a bug tracker and discussion board.
You can find the rom thread at here. http://forum.xda-developers.com/showthread.php?p=52641719
"Why didn't you create a dev-db?" You didn't read the above linked thread, did you?
THE ROM IS DISCONTINUED. ALL BUG REPORTS WILL BE IGNORED.

So this end...?!

LahKeda said:
So this end...?!
Click to expand...
Click to collapse
nah.. buddy this is not the end.. i'm just fed up with this phone..
anyone willing can continue from here.. or better build it from source,

If u can send some documents and resources to learn how to build roms please send it to me ...and I will try to build rom to this phone

psych.half said:
nah.. buddy this is not the end.. i'm just fed up with this phone..
anyone willing can continue from here.. or better build it from source,
Click to expand...
Click to collapse
Have any logs? I had given up due to the lack of the device.

Unjustified Dev said:
Have any logs? I had given up due to the lack of the device.
Click to expand...
Click to collapse
Logs.. oh logs.. hundreds of mb of logs.. @[email protected] Anyways latest log with h/w enabled is this..
Code:
E/libEGL ( 364): load_driver(/system/lib/egl/libEGL_mali.so): Cannot load library: soinfo_relocate(linker.cpp:1013):
cannot locate symbol "shim_eglSetBlobCacheFuncsANDROID" referenced by "libEGL_mali.so"...
E/libEGL ( 364): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 364): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)

psych.half said:
Logs.. oh logs.. hundreds of mb of logs.. @[email protected] Anyways latest log with h/w enabled is this..
Code:
E/libEGL ( 364): load_driver(/system/lib/egl/libEGL_mali.so): Cannot load library: soinfo_relocate(linker.cpp:1013): cannot locate symbol "shim_eglSetBlobCacheFuncsANDROID" referenced by "libEGL_mali.so"...
E/libEGL ( 364): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 364): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
Click to expand...
Click to collapse
go into stock system it can be a dump and open a terminal in lib folder and type grep -R "shim_eglSetBlobCacheFuncsANDROID" then you should know the blob missing maybe

Unjustified Dev said:
go into stock system it can be a dump and open a terminal in lib folder and type grep -R "shim_eglSetBlobCacheFuncsANDROID" then you should know the blob missing maybe
Click to expand...
Click to collapse
I already arm-readel all the symbols and stuffs..
If i had found it in stock libs, i would already have added that blobs... There isn't that symbol in the stock libs too... like wtf..

psych.half said:
I already arm-readel all the symbols and stuffs..
If i had found it in stock libs, i would already have added that blobs... There isn't that symbol in the stock libs too... like wtf..
Click to expand...
Click to collapse
Are you trying to use hwcomposer? Because I read you switched to sw rendering? It might be better to back to jellybean 4.1.2 where you have a fighting chance.

Unjustified Dev said:
Are you trying to use hwcomposer? Because I read you switched to sw rendering? It might be better to back to jellybean 4.1.2 where you have a fighting chance.
Click to expand...
Click to collapse
f***** found it,,!!!! hwcomposer working..
Code:
I/SPRDhwcomposer( 96): type=0, flags=00000000, handle=0x41416970, tr=00, blend=0105, {0,0,240,19}, {0,0,240,19}
and seems to me like.. gralloc didnt crash this time
Code:
I/SurfaceFlinger( 96): SurfaceFlinger is starting
I/SurfaceFlinger( 96): use dithering
I/SurfaceFlinger( 96): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
I/run-parts( 98): run-parts: /system/etc/init.d/50selinuxrelabel exited with code 1
D/libEGL ( 96): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 96): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 96): loaded /system/lib/egl/libGLESv2_mali.so
I/[Gralloc]( 96): using (fd=14)
I/[Gralloc]( 96): id = sc8810fb
I/[Gralloc]( 96): xres = 240 px
I/[Gralloc]( 96): yres = 320 px
I/[Gralloc]( 96): xres_virtual = 240 px
I/[Gralloc]( 96): yres_virtual = 640 px
I/[Gralloc]( 96): bpp = 32
I/[Gralloc]( 96): r = 0:8
I/[Gralloc]( 96): g = 8:8
I/[Gralloc]( 96): b = 16:8
I/[Gralloc]( 96): width = 50 mm (121.919998 dpi)
I/[Gralloc]( 96): height = 65 mm (125.046150 dpi)
I/[Gralloc]( 96): refresh rate = 60.00 Hz
I/SPRDhwcomposer( 96): fb_width = 240,fb_height = 320
E/SPRDhwcomposer( 96): alloc overlay buffer failed
E/SPRDhwcomposer( 96): tmp alloc overlay buffer failed
E/SurfaceFlinger( 96): composer device failed to initialize (Invalid argument)
I/SurfaceFlinger( 96): Using composer version 0.0
W/SurfaceFlinger( 96): getting VSYNC period from fb HAL: 16666666
W/SurfaceFlinger( 96): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
W/Trace ( 96): error opening trace file: No such file or directory (2)
I/SurfaceFlinger( 96): EGL informations:
I/SurfaceFlinger( 96): vendor : Android
I/SurfaceFlinger( 96): version : 1.4 Android META-EGL
I/SurfaceFlinger( 96): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer
I/SurfaceFlinger( 96): Client API: OpenGL_ES
I/SurfaceFlinger( 96): EGLSurface: 8-8-8-8, config=0x6000000a
I/SurfaceFlinger( 96): OpenGL ES informations:
I/SurfaceFlinger( 96): vendor : ARM
I/SurfaceFlinger( 96): renderer : Mali-300
I/SurfaceFlinger( 96): version : OpenGL ES-CM 1.1 Spreadtrum Build
I/SurfaceFlinger( 96): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_point_size_array GL_OES_point_sprite GL_OES_texture_npot GL_OES_query_matrix GL_OES_matrix_palette GL_OES_extended_matrix_palette GL_OES_compressed_ETC1_RGB8_texture GL_OES_EGL_image GL_OES_draw_texture GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_OES_framebuffer_object GL_OES_stencil8 GL_OES_depth24 GL_ARM_rgba8 GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL_OES_texture_cube_map GL_EXT_discard_framebuffer GL_EXT_robustness
I/SurfaceFlinger( 96): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 96): GL_MAX_VIEWPORT_DIMS = 4096 x 4096
D/SurfaceFlinger( 96): Screen acquired, type=0 flinger=0x40a80318
This means? Hw rendering will also work?? right??/
Well... screen now feels snappier..

Is This ROM Stable now ? Or ready to use ??

does it shows network .. i mean the data service is working or not??

pratyush02 said:
does it shows network .. i mean the data service is working or not??
Click to expand...
Click to collapse
fixing network is next to impossible... every time i try bootloop..

Om! Lp ChazZ said:
Is This ROM Stable now ? Or ready to use ??
Click to expand...
Click to collapse
not really... at least now hw rendering works...

Hi.No news about cm?

this is it
so this is it right
we all tried guys network can not be fixed by us
we need a real hardcore samsung cm dev who can fix it
but no other dev i know is ready to work for star
i hope we recieve a stable cm in the future
anyways thx to
all who helped to develop cm to what it is right now

@rchit said:
so this is it right
we all tried guys network can not be fixed by us
we need a real hardcore samsung cm dev who can fix it
but no other dev i know is ready to work for star
i hope we recieve a stable cm in the future
anyways thx to
all who helped to develop cm to what it is right now
Click to expand...
Click to collapse
this post was made when.. hw rendering seemed impossible to be fixed.. now that i have fixed it.. i realized that if you give up then everything is impossible...
check the upated OP and my new thread at dev section.. i am planning to continue.. not giving up this time..
and yeah.. samsung doesn't give sources of their proprietary libs.. so any real developer will have difficulties in fixing stuffs.. but they didn't give up on their devices.. and neither should we..
sammy doesnt give a s**t about this device, the devs don't give a s**t about this device.. just hoping that this may change doesnt do much.. we gotta step up ourselves and work for our own device...

psych.half said:
this post was made when.. hw rendering seemed impossible to be fixed.. now that i have fixed it.. i realized that if you give up then everything is impossible...
check the upated OP and my new thread at dev section.. i am planning to continue.. not giving up this time..
and yeah.. samsung doesn't give sources of their proprietary libs.. so any real developer will have difficulties in fixing stuffs.. but they didn't give up on their devices.. and neither should we..
sammy doesnt give a s**t about this device, the devs don't give a s**t about this device.. just hoping that this may change doesnt do much.. we gotta step up ourselves and work for our own device...
Click to expand...
Click to collapse
but we do give a s**t about the device so lets rock!!!
M down to help when m on pc

Really appreciate your hard work :good:
Hoping you can fix the RIL too :fingers-crossed:

work on single sim?

Related

Musings

I've been playing with quite a few apps lately and talking to a few of those developers.
they've written stuff that should be able to scale to our wvga resolution quite happily but doesn't with the streak.
So there's something odd going on, examples include aTakephone, shapewriter and several others.
Obvious candidate is that Dell did something odd when creating the custom UI, but [email protected] beginning to have a niggling suspicion that this isn't a 800x480 screen..
I may hasten to add that's pure conjecture, and most likely wrong, but there's something weird going on, anyone have any ideas?
everything scales REALLLY wierd.
i.e all icons are the same SIZE they would be on a 3.7" screen
surly these things are a set number of pixels in size ... which means they should scale up and be bigger.... but they don't everything is 3.7" sized ... in most app's
and is there any way you can actually get the resoultion
i think dell ahve done somthing to scale down objects so they look the correct size on the huge screen.. otherwise everything would be HUGE
there must be a way of detecting the real dpi and resolution of the screen, this is linux after all, but I haven't found it yet..
Dell could well have done something to stop the scaling, but I can't see what it is other than change the dpi.
thyd have to have the screen showing a larger dpi then it actually has to cause the objects to display the way they do
for example the adw launcher app drawer button is exactly the same size as my desire ... its not been stretched at all which means its been scaled down.
having gone through my entire repetoire of linux commands (lspci lsusb xdpyinfo etc etc) with no success I decided to dmesg > /sdcard/test.txt
guess what appeared right at the start?
Code:
[ 0.832653] load_565rle_image: Can not open /logo.rle
[ 0.834146] Registered led device: lcd-backlight
[ 0.834213] BootLog, -auo_init, ret=0
[ 0.834866] BootLog, +lcdc_adv7520_init
[ 0.834886] lcdc_adv7520_init(), HTX_720p_60
[ 0.836033] [Jackie] lcdc_probe(), pdev=0x9f000800, mfd=0x9faf8280
[ 0.846386] FrameBuffer[1] 1280x720 size=3686400 bytes is registered successfully!
[ 0.846460] load_565rle_image: Can not open /logo.rle
[ 0.847253] lcdc_hdmi_init(): i2c_add_driver...HDMI
now why does the HDMI get called so early, why is it called at all without the dock
and why is it the only reference to framebuffer?
Very very odd, just another reason I hope to see custom ROMs out there.
Is there a software program to take screenshots with of the device? That would give you the resolution.
.
screen shot shoot me, 480 x 800
so it is
we really need more support lol
yeah I did a clean boot today and dmesg again..
lots more interesting info and a 480x800 framebuffer call near the start
but also lots of debugger logging calls, is that normal with android devices?
Looking forward to seeing some custom roms for this, had another play with one today in O2 and its just amazing, but I am reluctant to give up my Desire with Android 2.2 without knowing when the Streak is getting either an official upgrade or custom roms.
Did "Logcat > dump.txt" and got a load more info
Code:
I/SurfaceFlinger( 1223): vendor : Android
I/SurfaceFlinger( 1223): version : 1.31 Android META-EGL
I/SurfaceFlinger( 1223): extensions:
I/SurfaceFlinger( 1223): Client API: OpenGL ES
I/EGLDisplaySurface( 1223): using (fd=23)
I/EGLDisplaySurface( 1223): id = msmfb31_10000
I/EGLDisplaySurface( 1223): xres = 480 px
I/EGLDisplaySurface( 1223): yres = 800 px
I/EGLDisplaySurface( 1223): xres_virtual = 480 px
I/EGLDisplaySurface( 1223): yres_virtual = 1600 px
I/EGLDisplaySurface( 1223): bpp = 16
I/EGLDisplaySurface( 1223): r = 11:5
I/EGLDisplaySurface( 1223): g = 5:6
I/EGLDisplaySurface( 1223): b = 0:5
I/EGLDisplaySurface( 1223): width = 76 mm (160.421051 dpi)
I/EGLDisplaySurface( 1223): height = 127 mm (160.000000 dpi)
and
Code:
W/HAL ( 1223): load: module=/system/lib/hw/copybit.qcom.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/copybit.qcom.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/copybit.8x50.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/copybit.8x50.so' not found
W/SurfaceFlinger( 1223): ro.sf.lcd_density not defined, using 160 dpi by default.
I/SurfaceFlinger( 1223): OpenGL informations:
I/SurfaceFlinger( 1223): vendor : Android
I/SurfaceFlinger( 1223): renderer : Android PixelFlinger 1.0
I/SurfaceFlinger( 1223): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 1223): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
W/HAL ( 1223): load: module=/system/lib/hw/copybit.qcom.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/copybit.qcom.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/copybit.8x50.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/copybit.8x50.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/overlay.qcom.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/overlay.qcom.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/overlay.8x50.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/overlay.8x50.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/overlay.default.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/overlay.default.so' not found
Wonder if those drivers are in the git...
I/EGLDisplaySurface( 1223): xres_virtual = 480 px
I/EGLDisplaySurface( 1223): yres_virtual = 1600 px
very strange
why would they scale only the yres....
anyway... we can pull the driver... if we got the kernel source thats the main thing
I'm now fairly convinced its using standard qualcomm surf kernel, don't even think we need specific dell drivers..
The yres_virtual is to allow screen panning I think and is fairly usual framebuffer behaviour.
well we could try and compile 2.1 or 2.2 and see what happens...
worst thing ... it wont boot....
not like were playing with radio so no chance of bricking.
finally got around to building from the codearoura git
kernel seems about same size as 4399 and I extracted ramdisk.img from the streak .
Thought I'd try fastboot boot zImage ramdisk.img as it appears to be a safe way of trying it (not writing permanently to device)
but "boot" gives me an error FAILED (remote: invalid command), so it may have been removed from the bootloader..
Don't really want to test flashing it as I'm away for a week on holibobs and would rather have a working streak than a non working one..

[Kernel][AOSP][2.6.35.9][UV][OC] PureGinger Kernel 25-DEC-2010

This is my own compiled kernel for NEXUS ONE based on the latest source from stock git (http://android.git.kernel.org/)
The branch I use is: android-msm-2.6.35
As I am using my own compiled ROM (PureFroyo) daily, and I am using the stock Froyo camera, I cannot use the IR's kernel (as it is merged with 720p)
Therefore, this triggers my initiative to compile my own kernel. Referenced from intersectRaven's ; Wildmonks ; pershoot ; cyanogen and some other kernels, I have made various adjustments (merge as well). So, here are the features of this ROM:
- intersectRaven's suggested frequency table in acpuclock-qsd8x50.c
- UV to 950mV
- OC to 1152MHz
- All CPU power governors
- 21 MB memory hack (thanks to coolbho3k)
- Target for stock camera, no 720p camera
- No audio boost
- Some minor changes referenced from wildmonks and intersectRaven (thanks!)
- Wifi, Froyo portable hotspot and camera work perfectly
- Not HAVS, but SVS instead
- Battery life is good for my nexus one
- Best match with stock / AOSP ROM
So, here is the link to the kernel, I would be grateful if you could help to test it and feedback whether it works for you (thanks~ ^_^)
Change Log:
2010-12-25 (Merry X'mas )
======================
- Rename to PureGinger
- Tested under AOSP gingerbread for a few days, very stable!
- Changed back to 950mV because 925mV seems not stable in Gingerbread
- Cherry-pick many commits... refer to my github
Link: http://www.mediafire.com/?dawr4f99t4fwc35
Mirror: http://www.4shared.com/file/6pNfdRiQ/PureGinger_26359_AXI_UV_SVS_12.html
File: PureGinger_2.6.35.9_AXI_UV_SVS_122110_223513.zip
MD5: 775007F8C1B549AAF5E18E40B0C704F5
2010-11-26
=========
- Changed to 925mV (UV). Seems running smooth for a few days
- Cherry-pick many commits from various sources (thanks stock, pershoot, raven, redstar, cyanogen, etc...)
- Enhanced ds2784 battery driver
- Other changes could be seen from my github
Link: http://www.mediafire.com/?52aa1h265w1tfau
Mirror: http://www.4shared.com/file/eqA2z7nW/PF_26357_AXI_UV_SVS_112610_014.html
File: PF_2.6.35.7_AXI_UV_SVS_112610_014525.zip
MD5: B17904841A9114BBB453FF4A94676CF2
2010-11-17
=========
- Cherry-pick many commits from various sources
- Kernel scheduler improvement (http://forum.xda-developers.com/showthread.php?t=841599)
Link: http://www.mediafire.com/?lw7mfll6b88qtqx
File: PF_2.6.35.7_AXI_UV_SVS_111710_215623.zip
MD5: 3CD0C4976F5DA7BBFBD42FE95C6A44CE
2010-11-05
=========
- Apply IR's latest oom modifications
- Cherry-pick some latest IR's, pershoot's, cyanogen's & experimental commits
Link: http://www.mediafire.com/?vpb49te3rxpf11z
File: PF_2.6.35.7_AXI_UV_SVS_110510_230204.zip
MD5: F2C2DEE6DF9485B52A5973B243602F6D
2010-11-02
=========
- Merge with a few latest IR's & Wildmonk's commits
- Source push to github
Link: http://www.mediafire.com/?m407xyaub6wuiby
File: PF_2.6.35.7_AXI_UV_SVS_110310_002259.zip
MD5: 3CBF9EFD6A11680FB46253111941CE1E
2010-10-31
=========
- Fix USB mount problem
- Added AXI rate tweak for performance and battery savings (IR's commit: 03ca24721e278eca034f)
Link: http://www.mediafire.com/?xx2sf66sntcrf2r
File: PF_2.6.35.7_AXI_UV_SVS_103110_000825.zip
MD5: 5F4D54E6E3BA63CDA0D35DE4756CC82B
2010-10-27
=========
- First version
Link: http://www.mediafire.com/?t9w73l8qi773qm3
File: PF_2.6.35.7_UV_SVS_signed_102710_012826.zip
MD5: D1EEEA92276BE7965679B1AB173B10B2
---------------------------------------------------------------
Installation procedures are just like what you are flashing with any other kernels (please make backup first):
Instructions:
1.) Reboot to recovery and flash the update zip directly.
OR
Instructions for zImage and bcm4329.ko driver extracted from the update.zip(from command line):
1.) adb remount
2.) adb push bcm4329.ko /system/lib/modules
3.) adb reboot bootloader
4.) fastboot flash zimage zImage
5.) fastboot reboot
---------------------------------------------------------------
Last thing: Please flash the kernel at your own risk Enjoy it.
---------------------------------------------------------------
* I am using my own compiled ROM: PureFroyo
* Source finally push to github: http://github.com/ardatdat/PureFroyo-Kernel
* (OLD) - Link to the 1st version kernel source code:
Part 1
http://www.mediafire.com/?a4q78ux2yy8r8j4
Part 2
http://www.mediafire.com/?yy7t2i9hotq5hg5
---------------------------------------------------------------
You need to post a link to your source code, or make it available for people somehow, according to this.
http://www.xda-developers.com/android/general-public-license-gpl-for-android-kernels/
wdfowty said:
You need to post a link to your source code, or make it available for people somehow, according to this.
http://www.xda-developers.com/android/general-public-license-gpl-for-android-kernels/
Click to expand...
Click to collapse
This is true. Please comply.
EDIT: Thank you. Great work!
wdfowty said:
You need to post a link to your source code, or make it available for people somehow, according to this.
http://www.xda-developers.com/android/general-public-license-gpl-for-android-kernels/
Click to expand...
Click to collapse
overground said:
This is true. Please comply.
Click to expand...
Click to collapse
Just get myself in front of the computer ~
Sure, I am packing the source now and will post the link soon.
Thanks for your prompting
Thank you so much. Since several weeks my wifi at home didn't work very well. I try some kernel with the nightly. Your kernel solved my problem
Source codes finally uploaded to mediafire
THANKSS
Amazing Kernel, just what I was looking for. This overclocks it to 1.152 AWESOME while undervolted and stock!!! The best!
Everyone trying this new kernel, PLEASE REPORT WHICH ROM & VERSION YOU ARE USING?
atlast a custom-kernel for us non 720p, will try when i get home from work iam runnning Geo411´s FRG83 rom.
ardatdat said:
Just get myself in front of the computer ~
Sure, I am packing the source now and will post the link soon.
Thanks for your prompting
Click to expand...
Click to collapse
No problem, wouldn't want your thread to get locked/removed for something like that.
mrdemo007 said:
atlast a custom-kernel for us non 720p, will try when i get home from work iam runnning Geo411´s FRG83 rom.
Click to expand...
Click to collapse
Interested to hear your experience. This kernel seems like a great match for Geo's ROM.
wdfowty said:
No problem, wouldn't want your thread to get locked/removed for something like that.
Click to expand...
Click to collapse
thanks, source already uploaded and link updated in #1 post
Arcarsenal said:
Interested to hear your experience. This kernel seems like a great match for Geo's ROM.
Click to expand...
Click to collapse
Me too, waiting for your report
Arcarsenal said:
Interested to hear your experience. This kernel seems like a great match for Geo's ROM.
Click to expand...
Click to collapse
just flashed it on Geo's ROM it seems everything is fine just need a little more time for testing....
Edit : excellent with Geo's ROM
Rom become more responsive and snappy and battery life is little improved
Been running this kernel with a rooted stock FRG83 ROM for a day now. So far VERY NICE!
One thing...I seem to have a problem with WiFi cutting out for a couple seconds every minute or so when I'm in Airplane mode. I work in a basement and I use airplane mode to keep the radio from killing my battery.
I know this is probably somewhat unique to me, but thought I would let you know.
This is exactly what I'm looking for! Thanks a lot!
Edit: I'm using Geo's Completely Stock Deodexed with busybox, FRG83. I cannot connect to wifi after flashing this kernel, here are my logcat.
D/Tethering( 96): eth0 is not a tetherable iface, ignoring
D/WifiService( 96): ACTION_BATTERY_CHANGED pluggedType: 2
D/WifiService( 96): acquireWifiLockLocked: WifiLock{NetworkLocationProvider ty
pe=2 [email protected]}
V/WifiStateTracker( 96): Connection to supplicant established, state=DISCONNEC
TED
D/NetworkStateTracker( 96): setDetailed state, old =DISCONNECTED and new state
=DISCONNECTED
D/LocationMasfClient( 96): getNetworkLocation(): Location not found in cache,
making network request
I/wpa_supplicant( 686): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00
:00:00
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
W/wpa_supplicant( 686): Failed to initiate AP scan.
V/WifiStateTracker( 96): Changing supplicant state: DISCONNECTED ==> SCANNING
D/NetworkStateTracker( 96): setDetailed state, old =DISCONNECTED and new state
=SCANNING
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
D/ConnectivityService( 96): Dropping ConnectivityChange for WIFI: DISCONNECTED
/SCANNING
V/WifiMonitor( 96): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:0
0:00:00:00]
D/dalvikvm( 96): GC_FOR_MALLOC freed 24258 objects / 1295032 bytes in 118ms
D/NativeCrypto( 96): Freeing OpenSSL session
D/LocationMasfClient( 96): getNetworkLocation(): Number of prefetched entries
1
D/LocationMasfClient( 96): getNetworkLocation(): Returning network location wi
th accuracy 1467.0
D/WifiService( 96): releaseWifiLockLocked: WifiLock{NetworkLocationProvider ty
pe=2 [email protected]}
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
W/wpa_supplicant( 686): Failed to initiate AP scan.
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
D/SntpClient( 96): request time failed: java.net.SocketTimeoutException: Conne
ction timed out
W/wpa_supplicant( 686): Failed to initiate AP scan.
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
D/AK8973 ( 75): Compass Start
I/power ( 96): *** set_screen_state 0
D/WifiService( 96): ACTION_SCREEN_OFF
D/WifiService( 96): setting ACTION_DEVICE_IDLE timer for 120,000 ms
D/SurfaceFlinger( 96): About to give-up screen, flinger = 0x125b18
D/AK8973 ( 75): Compass CLOSE
W/wpa_supplicant( 686): Failed to initiate AP scan.
D/StatusBar( 96): DISABLE_EXPAND: yes
D/GoogleLoginService( 204): onBind: Intent { act=android.accounts.AccountAuthen
ticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
D/dalvikvm( 204): GC_EXPLICIT freed 2276 objects / 120416 bytes in 70ms
D/dalvikvm( 411): GC_EXPLICIT freed 35 objects / 2000 bytes in 60ms
BTW, I hide the SSID of my wifi, and the encryption method is WPA2-PSK with AES. And when I connect my nexus one to laptop, there is no notification to ask me to mount the phone as a usb device or something like that. There should be an android, green or orange, depends on mounted or not, but I notice nothing happens when I connect.
Interesting.. Which radio are you using at the moment?
Using Geo411's latest ROM I get no USB SD mount notification, anyone else having this issue? I am using the latest Korean radio ROM as well.
Arcarsenal said:
Interesting.. Which radio are you using at the moment?
Click to expand...
Click to collapse
32.50.00.32U_5.12.00.08, the latest Korean radio.
niftydl said:
Using Geo411's latest ROM I get no USB SD mount notification, anyone else having this issue? I am using the latest Korean radio ROM as well.
Click to expand...
Click to collapse
Me.
For those of you with USB mount and WiFi issues are you all using the latest Korean radio? Have you tried downgrading the radio and seeing if the issues are resolved?
Is swap enabled or disabled?

[Q] Wildfire S Port.

Someone is successful to make a Porting, of the ROM of the Wildfire S, for our LG Optimus ONE?
It exists already for:
HTC Aria, Sony Ericsson X8, HTC myTouch 3G, HTC Wildfire, HTC Legend, LG Optimus GT540, Huawei IDEOS.
The Hardware of HTC Wildfire S, is similar to ours, but still nobody has been decided to carry this rom, for we.
Please, others members, of other forum, have already made it.
i agree having a Sense rom ported for Optimus One wud make me happy devs please look into it..+1 for above ..Also that way we get to have Adobe flashlite on our phones too i guess
Atm I don't think it will be to much interest in a Sense or a Miui rom since we are so close to GB. Afterwards maybe but we don't have to much of a workforce. Maybe if we set up a donation for acquiring dev phones it would be a start.
For LG GT540 port! And we no?
Sense ROM has been ported to LG Optimus GT540:
http://forum.xda-developers.com/showthread.php?t=1046051
And for our LG Optimus ONE, no, why??????????????
I'll try do a sense port. I need to start studying the GT540 sources and putting LG OO kernel in it
useless ... I have tried different kernel, but with negative results
-----
inutile... ho già provato con vari kernel ma con esiti negativi
Agreed, a ROM with sense would be juicy!
ciaox said:
I'll try do a sense port. I need to start studying the GT540 sources and putting LG OO kernel in it
Click to expand...
Click to collapse
We hope you do. Htc Sense gingerbread is the best port we can get. I hope some devs will also try.
Smells like useless work to me . In the end Sense is just a Launcher-like app with some improvements but those are meager and not something you would absolutely need
Zerobarat1 said:
Smells like useless work to me . In the end Sense is just a Launcher-like app with some improvements but those are meager and not something you would absolutely need
Click to expand...
Click to collapse
And what about the flash support ( or flashlite ) that sense has ... THAT would definitely be AWESOME if it could run on OO.
Even for IDEOS?
I communicate to you that the ROM Sense, has been ported for Huawei IDEOS
http://forum.xda-developers.com/showthread.php?t=927861
And for we nothing, that isn' t correct
Well I am trying to port Wildfire S official rom
I used the sys dump from Official ROM and after using modified boot.img with gingerbread kernel i find the Graphics lib's don't work
If anybody can give me a clue to fix this i can try to make this work on our beloved P500
Below is the logcat:
E/SurfaceFlinger( 1804): eglSwapBuffers: EGL error 0x3001 (EGL_NOT_INITIALIZED)
W/zipro ( 1814): Unable to open zip '/system/etc/customer/bootanimation.zip': No such file or directory
D/HtcBootAnimation( 1814): Get cid:SPCS_001
D/HtcBootAnimation( 1814): filepath:/system/customize/CID/SPCS_001.xml
D/HtcBootAnimation( 1814): Load /system/customize/CID/default.xml
D/HtcBootAnimation( 1814): Using OpenGL
E/HtcBootAnimation( 1814): Could not find width.
E/HtcBootAnimation( 1814): Could not find height.
E/HtcBootAnimation( 1814): Could not find framerate.
E/HtcBootAnimation( 1814): Could not find part1.
E/HtcBootAnimation( 1814): Could not find part2.
E/HtcBootAnimation( 1814): Could not find part3.
D/libEGL ( 1814): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1814): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 1814): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 1814): loaded /system/lib/egl/libGLESv2_adreno200.so
W/libEGL ( 1814): 0: eglInitialize(0x1) failed (EGL_SUCCESS)
Is here SENSE for O1 http://forum.xda-developers.com/showthread.php?t=1112398
by.adrian said:
Is here SENSE for O1 http://forum.xda-developers.com/showthread.php?t=1112398
Click to expand...
Click to collapse
That is froyo, he meant gingerbread wildfire s....
Sent using LGE Xda Secret phone
Bitter_Sugar said:
I used the sys dump from Official ROM and after using modified boot.img with gingerbread kernel i find the Graphics lib's don't work
If anybody can give me a clue to fix this i can try to make this work on our beloved P500
Below is the logcat:
E/SurfaceFlinger( 1804): eglSwapBuffers: EGL error 0x3001 (EGL_NOT_INITIALIZED)
W/zipro ( 1814): Unable to open zip '/system/etc/customer/bootanimation.zip': No such file or directory
D/HtcBootAnimation( 1814): Get cid:SPCS_001
D/HtcBootAnimation( 1814): filepath:/system/customize/CID/SPCS_001.xml
D/HtcBootAnimation( 1814): Load /system/customize/CID/default.xml
D/HtcBootAnimation( 1814): Using OpenGL
E/HtcBootAnimation( 1814): Could not find width.
E/HtcBootAnimation( 1814): Could not find height.
E/HtcBootAnimation( 1814): Could not find framerate.
E/HtcBootAnimation( 1814): Could not find part1.
E/HtcBootAnimation( 1814): Could not find part2.
E/HtcBootAnimation( 1814): Could not find part3.
D/libEGL ( 1814): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1814): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 1814): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 1814): loaded /system/lib/egl/libGLESv2_adreno200.so
W/libEGL ( 1814): 0: eglInitialize(0x1) failed (EGL_SUCCESS)
Click to expand...
Click to collapse
bootanimation directory is different for p500?
Yeah HTC seems to have all the settings and bootanimation.zip stored under /system/customize folder.
I am trying to port HTC Sense 2.1 (Gingerbread 2.3.3) to P500
So i need to start the port from the scratch as i don't have a reference to work on it.
Guys, Sense is not that great you know. My cousin bought a Wildfire S and after much inspection, its nothing great at all, the UI isn't that extraordinary. Sense even lack some basic commands that I'm used to on normal Gingerbread roms :/

Screen unlock won't work JB

Hi all,
I've got a little problem here and i was wondering if anyone can help please.
when i install CM10 or any other custom roms i get such an issue that power button works great, it can even lock my screen but when i press it for unlocking screen it doesn't unlock the screen is still black but pressing volume buttons makes sounds, i think screen is unlocked but it's stays black till i don't reboot with longpressing power button.
when i go back to ICS this problem is solved, but it's terrible OS so please someonehelp me
here is the logcat if someone can find out what the problem is
05-31 20:51:40.180 I/PowerManagerService( 406): Going to sleep by user request...
05-31 20:51:40.250 I/Choreographer( 406): Skipped 39 frames! The application may be doing too much work on its main thread.
05-31 20:51:40.250 D/MPLSensor( 406): handle : 4 en: 1
05-31 20:51:40.250 D/MPLSensor( 406): enabled_sensors: 16 dmp_started: 0
05-31 20:51:40.250 D/MPLSensor( 406): MLSetMPUSensors: 70
05-31 20:51:40.250 I/MPL-ml ( 406): Actual ODR: 25 Hz
05-31 20:51:40.250 D/MPLSensor( 406): set_power_states > MLDmpStart()
05-31 20:51:40.250 I/ ( 406): mpu3050_resume: Resuming to 0070
05-31 20:51:40.250 I/ ( 406): mpu3050_suspend: suspending sensors to 0000
05-31 20:51:40.250 I/ ( 406): mpu3050_suspend: Will resume next to 0070
Click to expand...
Click to collapse
At first sight it looks okay, are you sure you have the US bootloader installed?
DefQoN_BE said:
At first sight it looks okay, are you sure you have the US bootloader installed?
Click to expand...
Click to collapse
no i'm not. can u give me a link that i should flash?
I found out that the problem appears after rooting the device
FLaMpeR said:
no i'm not. can u give me a link that i should flash?
I found out that the problem appears after rooting the device
Click to expand...
Click to collapse
If you live in europe you probably have a UK bootloader installed, if you want to install cm 10.1 you need a US ICS bootloader, you can find the files for your device on www.droidbasement.com, click on your device name, download the US_LPL_4.0.4_bootloader.zip and flash it under PDA slot in ODIN
thanks a lot this worked for me
Sent from my Nexus 4 using Tapatalk 4 Beta
FLaMpeR said:
thanks a lot this worked for me
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
No problem

[Q] Help this newbie

ported many roms but this is my first rom which has not stuck in boot animation screen im happy but this logcat is kind of pain.(
E/logwrapper( 111): executing /system/bin/e2fsck failed: No such file or directory
E/ ( 171): coming in huawei_oem_rapi_streaming_function! event=213.
E/mm-camera( 153): qcamsvr_start: old_mode = 3f
E/mm-camera( 153): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 153): Cannot init Gesture library
E/cutils ( 143): Failed to read /data/.layout_version: No such file or directory
E/ ( 142): Qint android::get_number_of_cameras(): E
W/InterfaceController( 134): Warning (dlopen failed: library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
after booting the rom it show com.process.phone.android stopped working , systemui stopped woorking
what is the solution ? i cant locate system/lib/libnetcmdiface.so this file neither in base nor port rom..
for which device did you port we need more info....
Thanks for answering
vovaftw said:
for which device did you port we need more info....
Click to expand...
Click to collapse
i have ported for HUawei y201 Pro
USed rom made for Huawei G300
there are so much builds of Cm which are ported from g300 to y201 pro so i tried to port pac rom but faced this thing..
guide
vovaftw said:
for which device did you port we need more info....
Click to expand...
Click to collapse
please guide me .
Thanks
add me on Skype vova50006
ok
vovaftw said:
add me on Skype vova50006
Click to expand...
Click to collapse
thanks for ans im adding you

Categories

Resources