close this thread moderators please
hi,
I have a few q.
1. how did you solved custom lun file for mounting as MTP in recovery since I saw "status" working?
2. Did you fix repartition "issue"?
3. Why do you use https://github.com/omnirom/android_bootable_recovery 5.0 cose it's still under every day development??? (it can brick something)
4. Why don't you post changelog of your latest work or at least provide your github sources so that we can see what happend???
Cheers.
oh sorry i did not mean to anger you but status working means that the recovery is working. not fully working
and
i think Teamwin has made fixes
What's new in 2.8.5.0:
Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
Improve thread handling and move input handling into the main rendering thread to improve stability
Make MTP work even if unplugged and plugged back in
Unify scrollable list code and make kinetic scrolling feel more natural
Fix handling of mapped zip files for OTA updates (CM12 updater)
USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
Other small fixes and improvements
Don't know why U need busybox for it ( in flashable zip )
@Dhruvit Pokharna : Plagiarism my rule -_- . and why did you create a new reply whereas you can edit the previous reply ? whether you are the thanks hunter ?
Works on g355m single sim too?
cleverior.ipul said:
@Dhruvit Pokharna : Plagiarism my rule -_- . and why did you create a new reply whereas you can edit the previous reply ? whether you are the thanks hunter ?
Click to expand...
Click to collapse
ya , but now how can i close this thread
Build.prop
Build.prop from the start of developing the TWRP is changing.
It's not the same as build.prop for system.
It must contains original data from buildinfo.sh without Samsung Specific Properties and system.prop.
You don't need it for recovery.
You need the correct infos to identify the phone, couse I need it to identify it correctly via update script and
getprop check.
This build.prop from last build.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84Q
ro.build.display.id=omni_kanas3gnfcxx-eng 4.4.4 KTU84Q eng.darkside.20150116.102318 test-keys
ro.build.version.incremental=eng.darkside.20150116.102318
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Jan 16 11:47:26 CET 2015
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=darkside
ro.build.host=darkside-MS-7592
ro.build.tags=test-keys
ro.product.brand=samsung
ro.product.name=omni_kanas3gnfcxx
ro.product.board=kanas3gnfcxx
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=sc8830
# ro.build.product is obsolete; use ro.product.device
ro.build.product=kanas3gnfcxx
ro.product.model=kanas3gnfcxx
ro.product.device=kanas3gnfcxx
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=omni_kanas3gnfcxx-eng 4.4.4 KTU84Q eng.darkside.20150116.102318 test-keys
ro.build.fingerprint=samsung/omni_kanas3gnfcxx/kanas3gnfcxx:4.4.4/KTU84Q/eng.darkside.20150116.102318:eng/test-keys
ro.build.characteristics=default
ro.cm.device=kanas3gnfcxx
# end build properties
#
# from device/samsung/kanas3gnfcxx/system.prop
#
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=KOT49H.G355HNXXU0ANK2
ro.build.version.incremental=G355HNXXU0ANK2
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Wed Nov 26 18:17:29 KST 2014
ro.build.date.utc=0
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD5710
ro.build.tags=release-keys
ro.product.model=SM-G355HN
ro.product.brand=samsung
ro.product.name=kanas3gnfcxx
ro.product.device=kanas3gnfc
ro.product.board=sc7735s
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=sc8830
# ro.build.product is obsolete; use ro.product.device
ro.build.product=kanas3gnfc
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=kanas3gnfcxx-user 4.4.2 KOT49H G355HNXXU0ANK2 release-keys
ro.build.fingerprint=samsung/kanas3gnfcxx/kanas3gnfc:4.4.2/KOT49H/G355HNXXU0ANK2:user/release-keys
ro.build.characteristics=phone
ro.zygote.disable_gl_preload=false
# Samsung Specific Properties
ro.build.PDA=G355HNXXU0ANK2
ro.build.hidden_ver=G355HNXXU0ANK2
ro.build.changelist=3409105
ro.product_ship=true
ro.chipname=sc7735s
persist.sys.storage_preload=1
# end build properties
#
# from device/samsung/kanas3gnfc/system.prop
#
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.opengles.version=131072
ro.product.hardware=KANAS3GNFC_VE_V1.0.0
debug.hwui.render_dirty_regions=false
persist.ttydev=ttyVUART0
persist.storage.type=1
# delay for ConnectivityChange broadcast (ms)
conn.connectivity_change_delay = 0
ro.product.partitionpath=/dev/block/platform/sprd-sdhci.3/by-name/
persist.modem.w.enable=1
ro.modem.w.dev=/dev/cpw
ro.modem.w.tty=/dev/stty_w
ro.modem.w.eth=rmnet
ro.modem.w.snd=2
ro.modem.w.diag=/dev/slog_w
ro.modem.w.loop=/dev/spipe_w0
ro.modem.w.nv=/dev/spipe_w1
ro.modem.w.assert=/dev/spipe_w2
ro.modem.w.vbc=/dev/spipe_w6
ro.modem.w.id=0
ro.modem.w.fixnv_size=0x40000
ro.modem.w.runnv_size=0x60000
ro.modem.wcn.enable=1
ro.modem.wcn.dev=/dev/cpwcn
ro.modem.wcn.tty=/deiv/stty_wcn
ro.modem.wcn.diag=/dev/slog_wcn
ro.modem.wcn.assert=/dev/spipe_wcn2
ro.modem.wcn.id=1
ro.modem.wcn.count=1
# MultiTouch support
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
#Awesome player lateness in ms
awesome.lateness=200
gralloc.use_sync_mode=true
#Streaming player EOS timeout
nuplayer.eos.timeout=3
drm.service.enabled=1
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#Use vendor/platform codecs in Metadata retriever (for Hawaii H.264)
sf.metadata_use_plat_sw_codecs=1
#Use vendor/hw codecs in Metadata retriever
sf.metadata_retrv_hw_codecs=1
#turn off TREQ
persist.audio.pcmout1.sweq=OFF
persist.audio.pcmout2.sweq=OFF
#MULTISIM
ro.multisim.simslotcount=1
#EONS display
persist.eons.enabled=true
#Preload
persist.sys.storage_preload=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.sys.sprd.modemreset=0
persist.sys.sprd.wcnreset=1
ro.storage.flash_type=2
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.msms.phone_count=2
persist.msms.phone_count=2
persist.msms.phone_default=0
ro.modem.w.count=2
persist.sys.modem.diag=,gser
sys.usb.gser.count=4
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=96m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
ro.sf.lcd_density=240
ro.config.low_ram=true
ro.sec.fle.encryption=true
ro.build.scafe=macchiato
ro.build.scafe.size=short
ro.build.scafe.shot=single
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.error.receiver.default=com.samsung.receiver.error
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=4.4_r5
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
persist.sys.dalvik.vm.lib=libdvm.so
ro.kernel.android.checkjni=1
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
It's just mix of a system build.prop
No offence. Since I'm developing some goog stuff for G355HN I can't use same settings for G355H or
The recovery betwen GC2 models differs, recovery got to include specific build.prop and are mede for specific device.
I don't agree just because of the :
Code:
ro.build.product=kanas3gnfcxx
ro.product.model=kanas3gnfcxx
ro.product.device=kanas3gnfcxx
My phone and my model should have :
Code:
ro.product.model=SM-G355HN
ro.product.brand=samsung
ro.product.manufacturer=samsung
ro.product.name=kanas3gnfcxx
ro.product.device=kanas3gnfc
ro.product.board=sc7735s
ro.board.platform=sc8830
and ro.build.version info for system.
i do not understand ???
Obviously, he's a plagiator. I think that forum admins must check his work because of very strange behaviour. He opened some threads just after someone else do something new for our phone... Don't want to insult anyone, but i think that things are very clear about this!!
Sent from my SM-G355HN using XDA Free mobile app
hey i made the recovery and init.d support for g355h & g355m myself
i have only copied the ideas
have i made a rom ?
I'm not here to judge who is right, who is not, who has stolen something ??? ( GPL's are for that and I think they are open ... ), but have pointed to a direction for further update via recovery or update checks.
The recovery is only made for 1 model or on a basis of few models.
Stock recovery has more wide range of update and commands wia recovery, don't want to point to localization, pre or post init, procedures, events ...
Ok, it's not "official" but it a good way towards full nandroid backup, file operations, backups .... and all other small things that counts.
I have used Nandroid Online backup before ( 4 -6 months ago ) to make my own backup and my own script for this backups to work.
This is a need 4 sure, but still stock recoveries is simple but much more integrated into OS if U'r talking about stock things and updates. That doesn't bother me at all, couse now the time for create a full backup is realy small, couple of mins to create it and couple to restore.
If u have source why not compile it, it's on users to take risks.
I know some ppl are realy eager to test it, it is not a risk like su access and other things.
I use Y300 first TWRP recovery, havent test the CWM and I'm proud of ppl who want to share and teach and encorage other people to do the same.
What can I say, I'm really glad that I can help any1 and I'm reallly thankfull to the users who are willing to provide a guide how to and post some really nice posts.
Our device is not so good at development, but we made it what the device is now.
I'm glad I could participate in this, but couldn't make it without constant support of others ( don't want to point it out ).
I will still try to participate, but guess I will soon start with meizu MX4, guess there won't be so fun couse a lot of things is/were allready been made before I got this phone.
Thx to girls/guys who has helped me or I could help them.
I't not a farewell ...
I still haven't made my phone totaly unused ...
Still haven't and I guess I won't be so lucky ....
The time would/will telll ...
Related
Is this a Tegra 2 supporting image for a future asus device?
http://update.eeepc.asus.com/EP90/ASUS/EN/EE/update.aspkg
So I don't know what I'm looking at here, but I was reading about the ASUS EP90 which is a tegra 2 based tablet coming out sometime soon...
Given that, a little googling popped up this asus update path, after looking at the aspkg from a hex editor I realized it was a jar, when I extracted the contents it appears like an android system I think.. I don't know how to layout or configure one though.
Wonder what version it is or etc, anybody care to look and see?
Also, at http://update.eeepc.asus.com/EP90/ASUS/EN/EE/ there's a test folder with other update.aspkg (of different size) and other such stuff if you traverse around a bit
It's a Froyo system dump.
rswindle said:
Is this a Tegra 2 supporting image for a future asus device?
http://update.eeepc.asus.com/EP90/ASUS/EN/EE/update.aspkg
So I don't know what I'm looking at here, but I was reading about the ASUS EP90 which is a tegra 2 based tablet coming out sometime soon...
Given that, a little googling popped up this asus update path, after looking at the aspkg from a hex editor I realized it was a jar, when I extracted the contents it appears like an android system I think.. I don't know how to layout or configure one though.
Wonder what version it is or etc, anybody care to look and see?
Click to expand...
Click to collapse
Looks like a system dump with img files, there is even a recovery img on there.
The build.prop is showing:
HTML:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF91
ro.build.display.id=harmony-eng 2.2 FRF91 20101005.102124 test-keys
ro.build.version.incremental=20101005.102124
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Tue Oct 5 10:22:36 CST 2010
ro.build.date.utc=1286245356
ro.build.type=eng
ro.build.user=root
ro.build.host=nor-desktop
ro.build.tags=test-keys
ro.product.model=EP90_EU
ro.product.brand=Asus
ro.product.name=EP90
ro.product.device=harmony
ro.product.board=harmony
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=nvidia
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=harmony
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=harmony-eng 2.2 FRF91 20101005.102124 test-keys
ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101005.102124:eng/test-keys
# end build properties
#begin update properties
ro.update.PRODUCT_NAME=EP90
ro.update.OEM=ASUS
ro.update.LANGUAGE=EN
ro.update.SPECIAL=EE
ro.update.bspversion=10.8.3
ro.update.asusversion=00.02
ro.update.website=http://update.eeepc.asus.com/EP90/ASUS/EN/EE/update.aspkg
# end update properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.config.sync=no
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.browser.useragent=1
persist.service.mount.umsauto=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Oh neat, and it is for Tegra 2 it looks like then, wonder what it does on the g tab
Not development at all. Moved to general.
October 2010 - that's ancient.
T839UVKJ2
Code:
# autogenerated by buildinfo.sh
ro.build.id=FROYO
ro.build.display.id=FROYO.UVKJ2
ro.build.version.incremental=UVKJ2
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=2011. 10. 13. (목) 09:59:03 KST
ro.build.date.utc=1318467543
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-75
ro.build.tags=release-keys
ro.product.model=SGH-T839
ro.product.brand=samsung
ro.product.name=SGH-T839
ro.product.device=SGH-T839
ro.product.board=SGH-T839
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-T839
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-T839-user 2.2.1 FROYO UVKJ2 release-keys
ro.build.fingerprint=samsung/SGH-T839/SGH-T839/SGH-T839:2.2.1/FROYO/UVKJ2:user/release-keys
# Samsung Specific Properties
ro.build.PDA=T839UVKJ2
ro.build.hidden_ver=T839UVKJ2
ro.build.changelist=1069890
ro.tether.denied=false
# end build properties
Download:
Code:
http://hotfile.com/dl/132553035/4b1cb57/SGH-T839_T839UVKJ2_UV_TMB.rar.html
Pass: sampro.pl
What the point of posting these updates, they don't work on US devices.
Fresh Jr13 said:
What the point of posting these updates, they don't work on US devices.
Click to expand...
Click to collapse
Because this a US only forum.
hmmmmmmmmmmmmmmmmm
What devices do these work on? Which countries? Etc?
The ODIN does not work for this build period, it is not country relative.
Dumb question of the day: What's different about these builds?
They are developer builds, typically built by a buildbot, these include random bugfixes from the Samsung devs, they are still in testing so they may or may not work correctly.
sduvick said:
They are developer builds, typically built by a buildbot, these include random bugfixes from the Samsung devs, they are still in testing so they may or may not work correctly.
Click to expand...
Click to collapse
hmmm. well, is there a way to get them to work? I haven't been able to flash any other roms besides the KG2 via ODIN. Even with rooting and flashing CWM, no other roms will install via the SD Card. So, I was just curious. It seems like Samsung is continuing to work on this device and I'd be interested to see what they've come up with.
Look at the KJ2 deodexed flashable thread, that works, otherwise, try the new Glorious Overdose ROM, it's designed based on the KJ2 base.
I wonder if there have been any new developer builds for this device recently.
Nope this is still the latest one.
Sent from my HTC_Amaze_4G using XDA App
Przekret said:
Code:
http://hotfile.com/dl/132553035/4b1cb57/SGH-T839_T839UVKJ2_UV_TMB.rar.html
Pass: sampro.pl
Click to expand...
Click to collapse
This link no longer works. Does anyone have this? Could you please re-upload on Android File Host or a few file hosting services? Please?
Rapidshare link
build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=4.5.1-134_DFP-125
ro.build.display.id=4.5.1-134_DFP-125
ro.build.version.incremental=1317352186
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Thu Sep 29 08:33:23 CDT 2011
ro.build.date.utc=1317303203
ro.build.type=user
ro.build.user=hudsoncm
ro.build.host=il93lnxdroid52
ro.build.tags=release-keys
ro.product.model=MB526
ro.product.brand=MOTO
ro.product.name=MB526_RTCEE
ro.product.device=umts_jordan
ro.product.board=jordan
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=jordan_emara
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=umts_jordan_emara-user 2.3.5 4.5.1-134_DFP-125 1317352186 release-keys
ro.build.fingerprint=MOTO/MB526_RTCEE/umts_jordan:2.3.5/4.5.1-134_DFP-125/1317352186:user/release-keys
# end build properties
#
# system.prop for UMTS Jordan
#
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.default_usb_mode=0
# wlan interface
wifi.interface = tiwlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=32m
# System property for SMC
ro.service.start.smc=1
#proximit sensor screen off delay
mot.proximity.delay=450
#proximit sensor disable touch distance
mot.proximity.distance=60
#doesn't use Java DNS cache. Use only bionic cache.
networkaddress.cache.ttl=0
# BEGIN Motorola, drmn68, 13-July-2010, IKSTABLEONE-729
# true when phone launches UI successfully, default is flase
sys.mot.ui.launched=false
# END IKSTABLEONE-729
# BEGIN IKJORDANFR-65 Motorola, fpx478, default Mobile Hotspot is on
ro.mot.mynet=true
# END IKJORDANFR-65
# BEGIN Motorola, IKSTABLEFOURV-9197/9803/10119, IKPRODFOURV-168/453
ro.mot.bindervm.config=123
# END IKSTABLEFOURV-9197/9803/10119, IKPRODFOURV-168/453
# IKJORDAN-3341
windowsmgr.max_events_per_sec=70
#IKSHADOW-4638
# This defines the min duration between two pointer event in ms
ro.min_pointer_dur=10
# BEGIN, Motorola, qwp843, 12/06/2010, IKJRDNEM-3696
# Handle No audible indication while capturing photos in silent mode
# The property "ro.camera.sound.forced" is defined by google.
# Use "ro.camera.sound.forced" to decide whether camera shutter tone is forced: 1 forced; 0 not-forced.
ro.camera.sound.forced=0
# END IKJRDNEM-3696
#
# ADDITIONAL_BUILD_PROPERTIES
#
gsm.sim.mot.simswap=1
ro.config.ringtone=EtherShake.ogg
ro.mot.battmanager.wifictrl=0
ro.mot.hw.ringerswitch=0
rild.libpath=/system/lib/libril-moto-umts-1.so
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.default_usb_mode=0
ro.com.google.gmsversion=2.3_r7
ro.media.camcorder.vga=3gp,h264,24,4000000,aac,96000,44100,2
ro.media.camcorder.cif=3gp,h264,24,1500000,aac,96000,44100,2
ro.media.camcorder.qvga=3gp,h264,15,500000,aac,32000,16000,2
ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1
ro.media.camcorder.mmsres=qvga
ro.media.enc.aud.fileformat=amr
ro.media.enc.aud.codec=amrnb
ro.media.enc.aud.bps=12200
ro.media.enc.aud.ch=1
ro.media.enc.aud.hz=8000
ro.media.capture.maxres=5m
ro.media.capture.classification=classH
ro.media.capture.flip=horizontalandvertical
ro.media.capture.flash=led
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
ro.media.capture.shuttertone=1
ro.media.sensor.orient=90
ro.media.capture.panorama=0
ro.media.camerapreview.reg=480x360
ro.media.camerapreview.wide=848x480
ro.media.capture.slow.fps=60
ro.media.capture.fast.fps=4
ro.camcorder.VideoModes=false
ro.camera.DynamicFocus=false
media.stagefright.enable-record=false
media.stagefright.enable-rtsp=false
ro.blur.setupprovider.tmo=false
ro.blur.setup.silent=false
gsm.sim.mot.simswap=1
ro.com.motorola.smartsensor=true
ro.vf360_features.enabled=false
ro.blur_carrier_vodafone=false
ro.blur_carrier_tmo=false
ro.setupwizard.mode=DISABLED
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.mot.dpmext=true
ro.build.svn=11
ro.mot.hw.crystaltalk=1
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/motomb526/Profile/motomb526.rdf
ro.build.version.full=Blur_Version.45.0.1250.MB526.NonEFIGSRetail.en.EU
ro.mot.hidden_keyboards=evfwd
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.locationfeatures=1
ro.com.google.clientidbase.ms=android-motorola
languages: de (at), de, el, en (uk), en (us), es, es (us), fr, it, nl, pl
Thanks for your work.
It is Android 2.3.5.
thank you very much! but...could you tell me what are the differences between your 2.3.5 and 2.3.6? thanks in advance
I'm new to the Defy, and tried to search after 'CEE' in the forum. Have I understood correctly that this is a ROM without Motoblur?
It's full Blur this time. CEE = central/eastern Europe?
Aha, I see. So this is more of a localized ROM version for European users? Should I, as a user from Norway, use this ROM instead of this one then?
Hope I don't ruin your thread. Just got very curios about the CEE thing and couldn't find that much specific information about it.
Thank you for your work
Exactly what differences between 2.3.5 and 2.3.6?? I was waiting for this rom to my Defy but i would like to see how it works on full sbf. Any chance to get full sbf of this??
hachiueno said:
Aha, I see. So this is more of a localized ROM version for European users? Should I, as a user from Norway, use this ROM instead of this one then?
Hope I don't ruin your thread. Just got very curios about the CEE thing and couldn't find that much specific information about it.
Thank you for your work
Click to expand...
Click to collapse
There should be "Nordic" release somewhat soon with the way new localised roms pop up all the time.
Chamelleon said:
Exactly what differences between 2.3.5 and 2.3.6?? I was waiting for this rom to my Defy but i would like to see how it works on full sbf. Any chance to get full sbf of this??
Click to expand...
Click to collapse
No idea what the difference is as I have not tested many 2.3 Motorola roms.
No chance of SBF, this is a Nandroid backup done with retail Defy+. SBF files can be only obtained at service centers and updates, I think.
miscz said:
There should be "Nordic" release somewhat soon with the way new localised roms pop up all the time.
No idea what the difference is as I have not tested many 2.3 Motorola roms.
No chance of SBF, this is a Nandroid backup done with retail Defy+. SBF files can be only obtained at service centers and updates, I think.
Click to expand...
Click to collapse
So what exactly difference between flashing full sbf and nandroid except flashing process?? Is it mounted on old kernel or what??
Sorry for stupid question but Defy+ is my 2nd android phone and I'm still learning.
Here is the missing md5 file.
It is a normal full blur rom.
This rom has pt-br language?
Sent from my MB525 using XDA App
lmmfs said:
This rom has pt-br language?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
No support for pt.
walter79, will you extract missing polish translation for MS2Gigner or is polish team responsible for this? I could do this given the list of needed APKs.
does greenbread mod works?tested it didnt work
Does it work well with a Green Lensed Defy?
I wouldn't install it anyway, walter's MS2Ginger is more polished than stock software. I've posted it because some parts of this backup might be useful, for example polish translation team doesn't have to do translate all the apps by hand.
miscz said:
I wouldn't install it anyway, walter's MS2Ginger is more polished than stock software. I've posted it because some parts of this backup might be useful, for example polish translation team doesn't have to do translate all the apps by hand.
Click to expand...
Click to collapse
Is this ROM from your network operator?
Sent from Kepler-22b DEFYing Motorola
It was bought online from polish retail. T-Mobile doesn't have Defy+ yet AFAIK.
Can I (from full sbf 2.3.6) apply this nandroid?
fersago said:
Can I (from full sbf 2.3.6) apply this nandroid?
Click to expand...
Click to collapse
You can try...
Sent from Kepler-22b DEFYing Motorola
Android 2.3.6 multifiles
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XXKQ6
ro.build.version.incremental=XXKQ6
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Tue Feb 21 11:10:17 KST 2012
ro.build.date.utc=1329790217
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL163
ro.build.tags=release-keys
ro.product.model=GT-I9001
ro.product.brand=samsung
ro.product.name=GT-I9001
ro.product.device=GT-I9001
ro.product.board=GT-I9001
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9001
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9001-user 2.3.6 GINGERBREAD XXKQ6 release-keys
ro.build.fingerprint=samsung/GT-I9001/GT-I9001:2.3.6/GINGERBREAD/XXKQ6:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9001XXKQ6
ro.build.hidden_ver=I9001XXKQ6
ro.build.changelist=980980
ro.flash.resolution=720
# end build properties
Inside achive:
SMD_PDA_I9001XXKQ6_CL980980_REV00_user_low_ship_EMMC.smd.md5
SMD_CSC_GT-I9001-CSC-SERKP7_EMMC.smd.md5
SMD_MODEM_I9001XXKPK_CL977162_REV00_user_low_ship_EMMC.smd.md5
APBOOT_I9001XXKQ6_CL980980_REV00_user_low_ship_ONLY.tar.md5
AriesVE.ops
Click to expand...
Click to collapse
Download:
http://depositfiles.com/files/wzc8i9xef
http://narod.ru/disk/42303163001.e8af2ce4ba7eb2b029245ac293f278bd/I9001XXKQ6.ZIP.html
https://www.rapidshare.com/files/2473098865/I9001XXKQ6_2.3.6_.rar
Thanks 4pda.ru and nikopoll
another stock ?! I`m quite amazed that samsung gets new roms for SGS+ ...
mozgoder said:
Android 2.3.6 multifiles
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XXKQ6
ro.build.version.incremental=XXKQ6
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Tue Feb 21 11:10:17 KST 2012
ro.build.date.utc=1329790217
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL163
ro.build.tags=release-keys
ro.product.model=GT-I9001
ro.product.brand=samsung
ro.product.name=GT-I9001
ro.product.device=GT-I9001
ro.product.board=GT-I9001
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9001
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9001-user 2.3.6 GINGERBREAD XXKQ6 release-keys
ro.build.fingerprint=samsung/GT-I9001/GT-I9001:2.3.6/GINGERBREAD/XXKQ6:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9001XXKQ6
ro.build.hidden_ver=I9001XXKQ6
ro.build.changelist=980980
ro.flash.resolution=720
# end build properties
Inside achive:
Download:
http://depositfiles.com/files/wzc8i9xef
http://narod.ru/disk/42303163001.e8af2ce4ba7eb2b029245ac293f278bd/I9001XXKQ6.ZIP.html
Thanks 4pda.ru and nikopoll
Click to expand...
Click to collapse
Changelist?
uhh, I'm really surprised with two stocks was release in very short time.
Sweetez said:
uhh, I'm really surprised with two stocks was release in very short time.
Click to expand...
Click to collapse
Yeah, me too.Well, this shows that Samsung still cares about the development of this phone. Kudos to Samsung!
I wonder if i can use the european multi-CSC file from the XXKP4 ROM with this...
Really thought QK1 was the last one. maybe we even get android 2.3.7
Base of RC4 will be QK6
quendil said:
I wonder if i can use the european multi-CSC file from the XXKP4 ROM with this...
Click to expand...
Click to collapse
me to!
or if it would be useful and bring some benefits?
corrupt1234 said:
Yeah, me too.Well, this shows that Samsung still cares about the development of this phone. Kudos to Samsung!
Click to expand...
Click to collapse
It's called DEVELOPMENT and UPDATES when there is something to actually UPDATE. What was updated in this rom ?
I want a changelist, PRETTY PLEASE.
in a russian forum i read something about a new kernel and a new sms apk...
chasemyass said:
another stock ?! I`m quite amazed that samsung gets new roms for SGS+ ...
Click to expand...
Click to collapse
not really. this is still 2.3.6, its just for specific region. so not really consider as update. if they give us 2.3.7, that would be a different story
i thought this might of been the Value rom like the Galaxy S got.
nevermind
they should release for us those value pack instead of pushing 2.3.6. or don't tell me i9001 won't even get it
dr.wtf said:
in a russian forum i read something about a new kernel and a new sms apk...
Click to expand...
Click to collapse
wow that's all? We won't use the stock kernel so it's useless, I'm only interested in the sms apk actually but will use it as base for RC4 tho
this is btw the same story as ZSKP1 and ZSKP6. all mirrors suck btw, Ill upload it to sourceforge if the download is completed
On russian site 4pda.ru they say it is for service centers. I'v just flashed it.
It's android 2.3.6.
kernel 2.6.35.7-perf [email protected] #1
sn0vvman said:
On russian site 4pda.ru they say it is for service centers. I'v just flashed it.
It's android 2.3.6.
kernel 2.6.35.7-perf [email protected] #1
Click to expand...
Click to collapse
why for the service centers? does that mean it includes more/less bloatware? Because if they install it at the store they usually add unneeded apps
tested....
tested ... very slowly
hang on ..... wake up
Sometimes simply rebooting
not good!!!
Soul788 said:
tested ... very slowly
hang on ..... wake up
Sometimes simply rebooting
not good!!!
Click to expand...
Click to collapse
wow really? That sucks!
YES....
Sent from my GT-I9001 using Tapatalk
Originally Posted by Soul788
tested ... very slowly
hang on ..... wake up
Sometimes simply rebooting
not good!!!
Click to expand...
Click to collapse
Strange...
Din't faced something like this. Anyway it does not worse then the previouse official release.
why for the service centers? does that mean it includes more/less bloatware? Because if they install it at the store they usually add unneeded apps
Click to expand...
Click to collapse
I think it is because there are 4 parts and they could be flashed separately, for example modem part. Contains all usual Samsung stuff.
Does anyone think we will get 5.1 ROM soon?
TheROMGuy said:
Does anyone think we will get 5.1 ROM soon?
Click to expand...
Click to collapse
The soonest will probably be once 5.1 gets released to AOSP and CM updates to include it, but probably a few weeks away. As for official, who knows could be months.
Honestly, don't count on it. I beginning to regret getting the Opo after finding out that the official cm12s might take till April to be released. And that's just 5.0. I mean I'm sure someone is going to say to just do the nightlies but it's nice to have an official ROM put out by the Opo developers. They might include it when they release Oxygen OS but don't get your hopes up. It's all speculation.
gsmyth said:
The soonest will probably be once 5.1 gets released to AOSP and CM updates to include it, but probably a few weeks away. As for official, who knows could be months.
Click to expand...
Click to collapse
5.1 is already on AOSP. I hope Cyanogen gets on the ball with this one. Getting tired of waiting. xD Though I am a patient man. I can wait.
served24 said:
Honestly, don't count on it. I beginning to regret getting the Opo after finding out that the official cm12s might take till April to be released. And that's just 5.0. I mean I'm sure someone is going to say to just do the nightlies but it's nice to have an official ROM put out by the Opo developers. They might include it when they release Oxygen OS but don't get your hopes up. It's all speculation.
Click to expand...
Click to collapse
I don't regret getting my OPO I honestly love it. I couldn't ask for a better device. It's not the devices fault that Oneplus can't keep a deadline. Though honestly I'm on CM12 and IMHO it's quite great. I just miss the cm11s lockscreen. Whether or not the release OxygenOS doesn't matter to me. I know some of the Dev's here will eventually build Android 5.1
TheROMGuy said:
Does anyone think we will get 5.1 ROM soon?
Click to expand...
Click to collapse
You can get it as soon as you build it. Make it happen.
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
TheROMGuy said:
I know some of the Dev's here will eventually build Android 5.1
Click to expand...
Click to collapse
What are you waiting for? Seriously, grab the code and you won't have to worry about other people's inadequacy.
TheROMGuy said:
I don't regret getting my OPO I honestly love it. I couldn't ask for a better device. It's not the devices fault that Oneplus can't keep a deadline. Though honestly I'm on CM12 and IMHO it's quite great. I just miss the cm11s lockscreen. Whether or not the release OxygenOS doesn't matter to me. I know some of the Dev's here will eventually build Android 5.1
Click to expand...
Click to collapse
You do make a good point.
koe1974 said:
You can get it as soon as you build it. Make it happen.
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
What are you waiting for? Seriously, grab the code and you won't have to worry about other people's inadequacy.
Click to expand...
Click to collapse
As much as I would love to, I'm too busy with school. Also don't have Linux installed on any of my machines. I used to build from source for my HTC Vivid.
TheROMGuy said:
As much as I would love to, I'm too busy with school. Also don't have Linux installed on any of my machines. I used to build from source for my HTC Vivid.
Click to expand...
Click to collapse
began to build omni, they merged it already, still build errors - but with some changes everything should be fine!
If all goes well i will upload it later today
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47D
ro.build.display.id=omni_find7op-userdebug 5.1 LMY47D eng.olddroid.20150312.035227 test-keys
ro.build.version.incremental=eng.olddroid.20150312.035227
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.date=Thu Mar 12 03:54:51 PDT 2015
ro.build.date.utc=1426157691
ro.build.type=userdebug
ro.build.user=olddroid
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.build.flavor=omni_find7op-userdebug
ro.product.model=A0001
ro.product.brand=OnePlus
ro.product.board=find7op
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=OnePlus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=A0001
ro.product.model=A0001
ro.product.name=omni_find7op
ro.product.device=A0001
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=omni_find7op-userdebug 5.1 LMY47D eng.olddroid.20150312.035227 test-keys
ro.build.fingerprint=OnePlus/omni_find7op/find7op:5.1/LMY47D/olddroid03120354:userdebug/test-keys
ro.build.characteristics=default
ro.omni.device=find7op
# end build properties
OldDroid said:
began to build omni, they merged it already, still build errors - but with some changes everything should be fine!
If all goes well i will upload it later today
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47D
ro.build.display.id=omni_find7op-userdebug 5.1 LMY47D eng.olddroid.20150312.035227 test-keys
ro.build.version.incremental=eng.olddroid.20150312.035227
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.date=Thu Mar 12 03:54:51 PDT 2015
ro.build.date.utc=1426157691
ro.build.type=userdebug
ro.build.user=olddroid
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.build.flavor=omni_find7op-userdebug
ro.product.model=A0001
ro.product.brand=OnePlus
ro.product.board=find7op
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=OnePlus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=A0001
ro.product.model=A0001
ro.product.name=omni_find7op
ro.product.device=A0001
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=omni_find7op-userdebug 5.1 LMY47D eng.olddroid.20150312.035227 test-keys
ro.build.fingerprint=OnePlus/omni_find7op/find7op:5.1/LMY47D/olddroid03120354:userdebug/test-keys
ro.build.characteristics=default
ro.omni.device=find7op
# end build properties
Click to expand...
Click to collapse
Oh nice. Would love to see this built. Will probably switch if you get it posted up before CM12 gets built. Good job.
OldDroid said:
began to build omni, they merged it already, still build errors - but with some changes everything should be fine!
If all goes well i will upload it later today
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47D
ro.build.display.id=omni_find7op-userdebug 5.1 LMY47D eng.olddroid.20150312.035227 test-keys
ro.build.version.incremental=eng.olddroid.20150312.035227
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.date=Thu Mar 12 03:54:51 PDT 2015
ro.build.date.utc=1426157691
ro.build.type=userdebug
ro.build.user=olddroid
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.build.flavor=omni_find7op-userdebug
ro.product.model=A0001
ro.product.brand=OnePlus
ro.product.board=find7op
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=OnePlus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=A0001
ro.product.model=A0001
ro.product.name=omni_find7op
ro.product.device=A0001
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=omni_find7op-userdebug 5.1 LMY47D eng.olddroid.20150312.035227 test-keys
ro.build.fingerprint=OnePlus/omni_find7op/find7op:5.1/LMY47D/olddroid03120354:userdebug/test-keys
ro.build.characteristics=default
ro.omni.device=find7op
# end build properties
Click to expand...
Click to collapse
Great ! Waiting for it
Toll ! Warte schon gespannt drauf!
CM has yet to merge it and thus since nearly ALL of these ROMs depend on CM, we are dependent on them merging 5.1 and getting it to work with legacy code.
_ASSASSIN_ said:
CM has yet to merge it and thus since nearly ALL of these ROMs depend on CM, we are dependent on them merging 5.1 and getting it to work with legacy code.
Click to expand...
Click to collapse
CM has merged it ? ... Im noob or i see nothing on Gerrit ??
jamal2367 said:
CM has merged it ? ... Im noob or i see nothing on Gerrit ??
Click to expand...
Click to collapse
has yet to.. As in they have not merged it.
_ASSASSIN_ said:
has yet to.. As in they have not merged it.
Click to expand...
Click to collapse
OK thanks
As OldDroid said. Omni has merged it. But I think they are the only ones that have so far.
TheROMGuy said:
As OldDroid said. Omni has merged it. But I think they are the only ones that have so far.
Click to expand...
Click to collapse
Yep ! ..
and something is wrong with all devices out of nexus :/
fixed various build errors and got it compiled but it randomly crashes while booting :cyclops:
gonna kick a new build tonight before i go sleep .. wish me luck :angel:
someone said they merged it with omni but I don't think that's out for opo yet?
TheROMGuy said:
Oh nice. Would love to see this built. Will probably switch if you get it posted up before CM12 gets built. Good job.
Click to expand...
Click to collapse
OldDroid said:
began to build omni, they merged it already, still build errors - but with some changes everything should be fine!
If all goes well i will upload it later today
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47D
ro.build.display.id=omni_find7op-userdebug 5.1 LMY47D eng.olddroid.20150312.035227 test-keys
ro.build.version.incremental=eng.olddroid.20150312.035227
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.date=Thu Mar 12 03:54:51 PDT 2015
ro.build.date.utc=1426157691
ro.build.type=userdebug
ro.build.user=olddroid
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.build.flavor=omni_find7op-userdebug
ro.product.model=A0001
ro.product.brand=OnePlus
ro.product.board=find7op
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=OnePlus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=A0001
ro.product.model=A0001
ro.product.name=omni_find7op
ro.product.device=A0001
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=omni_find7op-userdebug 5.1 LMY47D eng.olddroid.20150312.035227 test-keys
ro.build.fingerprint=OnePlus/omni_find7op/find7op:5.1/LMY47D/olddroid03120354:userdebug/test-keys
ro.build.characteristics=default
ro.omni.device=find7op
# end build properties
Click to expand...
Click to collapse
Question: can it handle USB DACs? Because it doesn't look like CM12 is going to be able to.
served24 said:
Honestly, don't count on it. I beginning to regret getting the Opo after finding out that the official cm12s might take till April to be released. And that's just 5.0. I mean I'm sure someone is going to say to just do the nightlies but it's nice to have an official ROM put out by the Opo developers. They might include it when they release Oxygen OS but don't get your hopes up. It's all speculation.
Click to expand...
Click to collapse
I feel your pain. Personally, it's not just the time thing, it's the random things that REALLY should be at least half working by now, but hasn't improved in "how well it's working" since CM12 branch was first created. (USB DAC for example, I have been asking around about it since the early pre-nightly days, and the status has no improved one bit...in fact it's actually gotten a bit worse). I get that "it's only a nightly" blah blah...but think about it realistically, they haven't even made a slight improvement in terms of getting USB DACs to working properly with "NuPlayer" (the new player used internally in CM12 for playing/decoding all media, the previous one was called "awesomeplayer" iirc). And from what i can tell, we can expect the first batches of stable releases in a few weeks, I HIGHLY doubt they can fix the mess that is USB Audio by then.