Hi,
Will we have an ICS port from the Xperia Neo L ?
I read that this phone has the same hardware as Xperia Play
Just go on (talk.sonymobile.com/message/238221)
Thanks.
Max77230 said:
Hi,
Will we have an ICS port from the Xperia Neo L ?
I read that this phone has the same hardware as Xperia Play
Just go on (talk.sonymobile.com/message/238221)
Thanks.
Click to expand...
Click to collapse
Why would we need one.
Sent from R800x
it should have some improvements, will try and port in a few minutes
if i get a ftf or systemdump
hi nick,
I've found the .479 neo L firmware, it runs in setool2
(sonyericsson-world.com/files/file/3047-4-1-b-0-479-fsp-world-for-xperia-neo-l-mt25i-setool2/)
You need to create an account, and download is long (150kbps), but at the end you'll have your .sin_file_set firmware file, to test when you can.
Thanks.
There's an other file who contains kernel in (sonyericsson-world.com/files/file/3024-4-1-b-0-479-app-sw-generic-for-xperia-neo-l-mt25i-setool2/)
I've unpack files (with 7-zip) and create a .ftf bundle with flashtool and you should have a ~400Mb file.
Very good news !!!
I have flashed .479 neo L system and partitions (so no kernel and baseband, just software), and everything works but Wi-Fi. UI is very smooth. I will edit some news later.
Cheers.
What's going if i flash neo L baseband ? (flashed new baseband, it's -74, works well)
Okay, now with the modules from DooMKernel wifi works very well, but no hotspot.
Tested gamepad on Experiment 13 and all buttons works
Max77230 said:
Very good news !!!
I have flashed .479 neo L system and partitions (so no kernel and baseband, just software), and everything works but Wi-Fi. UI is very smooth. I will edit some news later.
Cheers.
What's going if i flash neo L baseband ? (flashed new baseband, it's -74, works well)
Okay, now with the modules from DooMKernel wifi works very well, but no hotspot.
Tested gamepad on Experiment 13 and all buttons works
Click to expand...
Click to collapse
And what happens if we flash the kernel? I never tried...
Wow, I don't get something Can someone please explain? How come we are able to just flash the neo l firmware and its seems more or less everything works? Is it because the Neo L specs are basically identical to the Play's ?
It would be great if DooMLord can make a custom kernel with the .479 sources that was provided by sony last week (developer.sonymobile.com/wportal/devworld/downloads/download/41b0479tarbz2). I think the ROM will be more optimize (Wi-Fi), and it's a real gift by sony as the fact is that the MT25i il a clean copy of the PLAY without gamepad.
@fareed
It's because neo L has the zeus hardware, just in rev.2 (no gamepad), so that's why i said that if we make a custom kernel with the neo L sources we can get all working, cause at the moment i suffer wifi issues (need doomlord modules cause of no stock kernel, and no hotspot).
@vokal
I will try to flash it tomorrow and i will send you the result.
Edit : wow, amazing ! incredible ! it seems that gamepad is integrated, i tried it on PES2012 and it works, also L and R.
I think that just the touchpad doesn't work. Wait for a patch, i will look at xDark work.
So anyone Know where i can upload my ROM to share it ?
Max77230 said:
@fareed
It's because neo L has the zeus hardware, just in rev.2 (no gamepad), so that's why i said that if we make a custom kernel with the neo L sources we can get all working, cause at the moment i suffer wifi issues (need doomlord modules cause of no stock kernel, and no hotspot).
@vokal
I will try to flash it tomorrow and i will send you the result.
Edit : wow, amazing ! incredible ! it seems that gamepad is integrated, i tried it on PES2012 and it works, also L and R.
I think that just the touchpad doesn't work. Wait for a patch, i will look at xDark work.
So anyone Know where i can upload my ROM to share it ?
Click to expand...
Click to collapse
I can confirm that the System partition does in fact install and boots fine, but I allways get Keyboard FC's and alot of stuff didnt got installed :S
Edit: here is the Build.prop, found some funny things:
Code:
##### Merging of the /util/data/semc_kernel_time_stamp.prop file #####
ro.build.date=Thu May 24 16:12:14 2012
ro.build.date.utc=1337868734
ro.build.user=BuildUser
ro.build.host=BuildHost
##### Final patch of properties #####
ro.build.product=MT25i
ro.build.description=MT25i-user 4.0.4 4.1.B.0.479 IL5_3w test-keys
ro.product.brand=SEMC
ro.product.name=MT25i_1265-5721
ro.product.device=MT25i
ro.build.tags=release-keys
ro.build.fingerprint=SEMC/MT25i_1265-5721/MT25i:4.0.4/4.1.B.0.479/IL5_3w:user/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1265-5721
ro.semc.version.cust_revision=R2I
persist.ro.ril.sms_sync_sending=1
ro.settings.apn.lock=ä¸*国移动互è”网,ä¸*国è”通互è”网,ä¸*国移动MMS,ä¸*国移动WAP,ä¸*国è”通MMS,ä¸*国è”通WAP
#########################################################################
ro.config.ringtone=xperia.ogg
ro.config.notification_sound=notification.ogg
ro.config.alarm_alert=alarm.ogg
ro.semc.content.number=PA1
################# Updating of the SW Version #################
ro.semc.version.fs_revision=4.1.B.0.479
ro.build.id=4.1.B.0.479
ro.build.display.id=4.1.B.0.479
##### Values from product package metadata #####
ro.semc.product.model=MT25i
ro.semc.ms_type_id=PM-0110-BV
ro.semc.version.fs=WORLD-i
ro.semc.product.name=Sony Xperiaâ„¢ neo L
ro.semc.product.device=MT25
ro.product.model=MT25i
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.incremental=IL5_3w
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.type=user
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony Ericsson
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.characteristics=default
# end build properties
#
# system.prop for phoenix
#
# Notify the system that the RIL only signals once
ro.telephony.call_ring.multiple=0
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1
ro.semc.timescape_keys=Sony_Ericsson_Xperia_PLAY
#Automount restored because of the exclusion backcover HW key operation.
#ro.product.sdcard.automount=0
ro.semc.sols.product-code=107
ro.semc.sols.company-code=5
# Disable strict mode checking
persist.android.strictmode=0
# Constant values for Battery test in Service menu
ro.semc.batt.capacity=1500
ro.semc.batt.test.z_threshold=50
ro.semc.batt.test.min_level=70
#Default values/Locales for the hiding languages feature
ro.product.locale.excluded=ar_EG ar_IL fa_IR iw_IL
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=framework/SemcGenericUxpRes.apk
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-sonyericsson
drm.service.enabled=true
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.semc.xloud.supported=true
ro.sf.lcd_density=240
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.semc.dashboard.xperiaplay=true
ro.semc.dashboard.searchuri=http://pss.dl.playstation.net/pss/content/list.html
ro.usb.pid_suffix=17C
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.drm.active.num=4
ro.drm.active.0=semc,1
ro.drm.active.1=cmla,0
ro.drm.active.2=viaccess,0
ro.drm.active.3=marlin,1
Also found some xperia play stuff on framework
Going to update my NeoS rom with these
Ohh thanks. Media fire is good for hosting but I have my own website and hosting so I'd be more than happy to host your files. Just pm me for details
Vokal,
For the keyboard FC, I've solve it, do a full Wipe,(data+dalvik+cache), and I've flash vendor partition for uninstalled apk's.
resume for people who want to try this ROM :
Fresh install : Do a full wipe
- flash system + userdata+vendor(partitions)
- if you want more you can flash all but kernel (I found that the new -74 baseband has a better signal reception).
@fareeed : How can I send you my files ? i'm okay but does it'll cost me anything ? cause i'm only 17 and i don't have something to pay.
Max77230 said:
Vokal,
For the keyboard FC, I've solve it, do a full Wipe,(data+dalvik+cache), and I've flash vendor partition for uninstalled apk's.
resume for people who wnt to try this ROM :
Fresh install : Do a full wipe
- flash system + userdata+vendor(partitions)
- if you want more you can flash all but kernel (I found that the new -74 baseband has a better signal reception).
@fareeed : How can I send you my files ? i'm okay but does it'll cost me anything ? cause i'm only 17 and i don't have something to pay.
Click to expand...
Click to collapse
Baseband -74 works Great! flashed the rom wih the new xperia game launcher it didnt installed, the old one works fine, going to test if the touchpads work on minecraft. Does anyone know if they worked on ICS Beta? I mean in Minecraft.
Thanks!
vokal1992 said:
Baseband -74 works Great! flashed the rom wih the new xperia game launcher it didnt installed, the old one works fine, going to test if the touchpads work on minecraft. Does anyone know if they worked on ICS Beta? I mean in Minecraft.
Thanks!
Click to expand...
Click to collapse
Vokal maybe we could use the sources from Neo L ICS 4.0.4 and put them into our ICS 4.0.4 roms to increase stability and speed.... If this iss faster that is.
If only I could use my phone I would of done this myself.
I've flash the new kernel. Wifi works without modules but always no hotspot, and a new problem. Luminosity is so low when is set to automatic. So it looks the same but in waiting for kernel optimizations, i roll back to ICS beta kernel.
PS : the camera image is also inverted, and no more gamepad !(Edit : No more root also)
@Vokal : Yes, Touchpads worked on Minecraft in ICS beta.
Max77230 said:
I've flash the new kernel. Wifi works without modules but always no hotspot, and a new problem. Luminosity is so low when is set to automatic. So it looks the same but in waiting for kernel optimizations, i roll back to ICS beta kernel.
PS : the camera image is also inverted, and no more gamepad !(Edit : No more root also)
@Vokal : Yes, Touchpads worked on Minecraft in ICS beta.
Click to expand...
Click to collapse
flashed the camera from the ICS beta and its fixed now
Oh, I've drive you in error, hotspot works !
So i think i've finish for today and i'm really happy for the fact that everything works with ICS beta kernel (but no touchpads) and it's the best rom i've seen on XPlay, very smooth. I'll give a try on Antutu before sleeping.
Edit : I managed to get a 3100 score in antutu at stock, with a very good score in 3D, this ROM looks promising, better than xDark ICS.
Tomorrow i will look at his touchpad patch, and someone can explain to me what's the incidence of mt25i in build.prop, as it would be r800i ?
Max77230 said:
Oh, I've drive you in error, hotspot works !
So i think i've finish for today and i'm really happy for the fact that everything works with ICS beta kernel (but no touchpads) and it's the best rom i've seen on XPlay, very smooth. I'll give a try on Antutu before sleeping.
Click to expand...
Click to collapse
WOOOOOW flashed the whole firmware, including the kernel and it works!!!!! yeah!!!!!
Well, it smells good for locked bootloaders ! Have you the same problems as me ? (luminosity, gamepad, camera-seems that you've fixed it).
Max77230 said:
Well, it smells good for locked bootloaders ! Have you the same problems as me ? (luminosity, gamepad, camera-look like you've fixed it).
Click to expand...
Click to collapse
yeah the big problem is to gain root now, so people with locked bootloaders can flash fixes or custom roms based on stock
Edit: Just Got Root and Clockworkmod!
Related
ANDROID SDK 2.0 is released, and I hope some of you devs/chefs wil use it to build a new custom rom for us Hero fans.
It has the multitouch feature for keyboard etc activated and build in.
O i want 2.0 so bad getting rid of the htc skin called sense (it's fun to have but not more then that!) and go like real android
If i knew enought to cook a (2.0) rom myself i would take this day of from work and will strugle til i get something working for the Hero
I will reward the dev who makes a working 2.0 ROM (with at least 90%+ working hardware) with 50 dollars (ofcourse for the HERO!)
Count my $20 in.
Why did you put this at the dev board? There is a similar one in the discussion board with more information.
As you can see here is where the real money is
You guys don't really seem to realize what it means when the SDK is released.
The same happened when the 1.6 SDK is released.
It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.
jaapschaap said:
As you can see here is where the real money is
Click to expand...
Click to collapse
If that's the case I might as well chip in with a twenty ;-p
It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.
Click to expand...
Click to collapse
I knew it but because of the TS his story i start believing it can be transfomrt into a ROM
dream owners using eclair rom. not the full rom but usuable. at least they can test it.
dipje said:
You guys don't really seem to realize what it means when the SDK is released.
The same happened when the 1.6 SDK is released.
It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.
Click to expand...
Click to collapse
Yes and no.
Take a look at platforms\android-2.0\images\ in your SDK.
;]
Not a rls, but at least something to play with.
adwinp said:
Yes and no.
Take a look at platforms\android-2.0\images\ in your SDK.
;]
Not a rls, but at least something to play with.
Click to expand...
Click to collapse
Those are emulator images, not made for a specific handset, therefore they don't work correctly if you flash then or repackage the contents to update.zip's!
Look at dream board and you'll see the issues with the DEV 2.0 ROM
True, then again, what do we have unyaffs for?
i just want 2.0 to come out, now. with moto droid coming out on nov. 1, it shouldnt be hard to port hopefully. im really in love with android 2.0 and i prefer it to the sense ui, it looks so much nicer
im really excited bout what htc is doing about android2 and their sense, since android2 looks nice now either ;-) hopefully we get a sexy merge of both!
Here's the build.prop, but might as well take a look the the updated apks...
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ECLAIR
ro.build.display.id=sdk-eng 2.0 ECLAIR 17704 test-keys
ro.build.version.incremental=17704
ro.build.version.sdk=5
ro.build.version.codename=REL
ro.build.version.release=2.0
ro.build.date=Thu Oct 22 01:18:16 PDT 2009
ro.build.date.utc=1256199496
ro.build.type=eng
ro.build.user=android-build
ro.build.host=apa4.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=sdk
ro.product.brand=generic
ro.product.name=sdk
ro.product.device=generic
ro.product.board=
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=ldpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=sdk-eng 2.0 ECLAIR 17704 test-keys
ro.build.fingerprint=generic/sdk/generic/:2.0/ECLAIR/17704:eng/test-keys
# end build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
[ROM] XWJV1 - beta 2.3.2 Gingerbread! Confirmed!
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWJV1
ro.build.version.incremental=XWJV1
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.2
Link to ROM: http://www.multiupload.com/OH1LRZDN3N
This ROM is from Polish forum: http://forum.android.com.pl/f193/i9000rom-gingerbread-xwjv1-54618/
Credits: goofoos
BEFORE YOU POST ANY QUESTIONS:
ROM:
It is a full ROM from Samsung, it is a beta build so don't expect too much!
Only flashable through Odin/Heimdal
Pit File is 512 but it seems like 803 also works
nitr8 released a rooted and flashable JV1 also thanks to TrOjAnUK
Only recovery 2e available, no CWM.
This ROM will not work with any of the custom kernels available right now! Kernel sources will be published around the official (KIES) release of the first Gingerbread ROM by Samsung. No kernel developer can build a kernel for any Gingerbread ROM until then. thx MrBusiness
Functionality and issues:
bhola made and promoted (excessively) 2 videos (Tutorial & Quick look)
All bands seem to be enabled, thx Nausicaa647
Swype fix by nitr8 thx Rawat for implementing
There appear to be incompatibilities with apps, some apks (especially games) won't work properly
TouchWiz 3 is installed (GameHub not included since it's part of TW4 as stated by skiddhard)
Market does work
Recovery Mode is working, just release the buttons as soon as the Samsung Logo appears thx galaxoid
GPS works thx iammodo
The Kernel just supports ext4, out of the box it's still rfs.
While browsing you may encounter "Kernel Panic"
Customization, root, modding:
Chainfire already rooted it
Daneshm90 enabled the lock animation use ADB to replace the framework.apk
[Ramad] Deodexed and Zipaligned apks of JV1
Stock Gingerbread Launcher thx Daneshm90
Rawat also made alternative Icons
(thx theduckking)
SGS running android 2.3 -- http://www.youtube.com/watch?v=R7Fb7pLZX3M
How to install Android 2.3.2: http://www.theandroidsoul.com/how-to-install-android-2-3-2-on-samsung-galaxy-s-leaked-rom/ (thx itskapil)
WOWOWOWOOWOWOW!!!!!!!!!!!!!!!!
Finally Gingerbread Released!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I hope it will work well!!
So Let's go cooking some custom Gingerbread ROM.....
first, I do not want to steal your credit!
is it this one?
http://www.megaupload.com/?d=RIGPRRCW
a Polish board aparently confirms this to be gingerbread...
Lorbas said:
Not tested this one
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWJV1
ro.build.version.incremental=XWJV1
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.2
Link in few minutes
Click to expand...
Click to collapse
Where from? Nothing in Samfirmware...
So let's wait... I won't believe until I see.
GMH24 said:
first, I do not want to steal your credit!
is it this one?
http://www.megaupload.com/?d=RIGPRRCW
a Polish board aparently confirms this to be gingerbread...
Click to expand...
Click to collapse
Broken link. Or at least for me.
Can anyone confirm? And can modded kernels be used on this?
I'm trying not to get VERY exited. Also, i've found link; http://www.megaupload.com/?d=RIGPRRCW
Not tested. And not only me, lol.
Well, before we can add some custom kernel we have to root this FW
here is the link to the Polish forum:
http://forum.android.com.pl/f193/xwjv1-54618/
mulitupload link is in the first post!
http://www.megaupload.com/?d=RIGPRRCW
EDIT: $hit, the links seems to be down! but my download is still running...
It's a big firmware 241 MB. Thanks for info.
PREMIUM LINK (36H)
Ok, seems like it's gonna be worth checking
But... What if this will bring new bootloader.
LINK IS DOWN! Can someone repost it?
GMH24 said:
first, I do not want to steal your credit!
is it this one?
http://www.megaupload.com/?d=RIGPRRCW
a Polish board aparently confirms this to be gingerbread...
Click to expand...
Click to collapse
it's the same, now let's cook
Nice news !!!
Gingerbread with touchwizz 4 ?
Sent from my Galaxy S running CM7
Maybe it will update the Bootloader this ROM......
I'm downloading it right now....let's see how it's made!
If it will update the bootloader, I hope it won't block the Download Mode!
People, can you add mirrors? wanna try it right away
Jodelaplaya said:
Nice news !!!
Gingerbread with touchwizz 4 ?
Sent from my Galaxy S running CM7
Click to expand...
Click to collapse
I'll take everything as long it's gingerbread.
btw. OP, since it is gingerbread you might want to change the "?" in your title to a "!!!!!!! FU** YEAH!" or something alike^^
I'm nearly peeing myself, I'll get the screenlock animation I always wished for
Edit:
You can read minds my friend
Flashing now. Wish me luck.
I927UCKI3:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.UCKI3
ro.build.version.incremental=UCKI3
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Fri Sep 23 11:16:36 KST 2011
ro.build.date.utc=1316744196
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-79
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I927
ro.product.brand=samsung
ro.product.name=SGH-I927
ro.product.device=SGH-I927
ro.product.board=SGH-I927
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927UCKI3
ro.build.hidden_ver=I927UCKI3
ro.build.changelist=601619
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=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927-user 2.3.5 GINGERBREAD UCKI3 release-keys
ro.build.fingerprint=samsung/SGH-I927/SGH-I927:2.3.5/GINGERBREAD/UCKI3:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I927UCKI3
ro.build.hidden_ver=I927UCKI3
ro.build.changelist=601619
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Download:
http://hotfile.com/dl/137505177/0a48afe/SGH-I927_ATT_I927UCKI3.rar.html
Pass: sampro.pl
So what's different about this ROM?
Rockwig said:
So what's different about this ROM?
Click to expand...
Click to collapse
Well, we dont know until we try it. A letter change is usually a bigger update than a letter so we know at least a few things have i changed, i hope it has the black gallery fix...
Usually when I ROM is posted, a change log is posted as well. That would be nice in this. At least so there is some idea on what people could be flashing.
Rockwig said:
Usually when I ROM is posted, a change log is posted as well. That would be nice in this. At least so there is some idea on what people could be flashing.
Click to expand...
Click to collapse
Looking at his other posts, I think its an update to the official stock firmware. Probably leaked.
Nice thanks!
Has anyone tried this rom yet? Any news on the differences?
Sent from my SAMSUNG-SGH-I927 using XDA App
This is a firmware update leaked by Samsung. It will be stock, no root, no CW Recovery. All carrier bloatware will be in place.
Assuming this works the same as the I897 leaks, you'll need Odin to install it.
Przekret is great posting the newest "official" leaks so when you see him posting ROMs it's safe to assume it'll be a stock leak. He has been great in providing leaks for the I897 devs and us ROM flashaholics.
Thanks so much.It is always nice to see new updates and people willing to share with us ;-)
is this the latest stock rom?
As far as I know the latest version is 2.3.6.
shinydesert said:
As far as I know the latest version is 2.3.6.
Click to expand...
Click to collapse
Can u provide me a link or a system dump?i m gonna make a custom rom.
I was able to download it last Friday night,but right after that I changed the kernel and installed a rooted 2.3.5 version.
Last night I checked for new updates and the device downloaded the new update but the installation failed,if you think there is a way to find those new files I will be more than glad to dig into the phone.
any noticeable difference b/w the 2?(performance,i mean)
u shud have had a nandroid backup
sakindia123 said:
any noticeable difference b/w the 2?(performance,i mean)
u shud have had a nandroid backup
Click to expand...
Click to collapse
I don't think 2.3.6 added anything significant other than a really minor 'feature' so I suggest working with 2.3.5 if no one comes forth with a 2.3.6 dump soon.
vil33 said:
I don't think 2.3.6 added anything significant other than a really minor 'feature' so I suggest working with 2.3.5 if no one comes forth with a 2.3.6 dump soon.
Click to expand...
Click to collapse
so i started makin a rom based on this.
Ps-U have a hell lot of bloatware!
This is a stock firmware leak...that alone should tell you it will have all of at&t's bloatware in it.
Rogers ROM is a better starting point in my opinion. It's very similar to AT&T but there is manual operator setup in networks and delivery reports for messages. Both features are missing in AT&T ROM but are quite useable.
too bad.i already made the rom as i couldnt find any other
SGH-I927/ATT/I927UCKI3/I927ATTKI3/I927UCKI3
from this (2.3.5) somebody have 4 files version with pit?
I looking for...!!!
I have the leaked version of ICS installed on my A100, I didn't get the Official version over the air. Is there any way to downgrade to Honeycomb to get the official as the leaked version has been giving my tablet camera issues with green flickering etc.
Here is my build.prop
build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=Acer_AV041_A100_0.009.00_WW_GEN1
ro.build.version.incremental=1331290290
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Mar 9 18:52:40 CST 2012
ro.build.date.utc=1331290360
ro.build.type=user
ro.build.user=pandora
ro.build.host=pandora03
ro.build.tags=release-keys
ro.build.sku=WW_GEN1
ro.product.model=A100
ro.product.brand=acer
ro.product.name=a100_ww_gen1
ro.product.device=vangogh
ro.product.board=vangogh
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Acer
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=vangogh
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=a100_ww_gen1-user 4.0.3 IML74K 1331290290 release-keys
ro.build.fingerprint=acer/a100_ww_gen1/vangogh:4.0.3/IML74K/1331290290:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version=131072
wifi.interface=wlan0
keyguard.no_require_sim=1
ro.dinfo.version=1.0
ro.cpu.vendor=nVidia
ro.cpu.speed=1.0 GHz
ro.cpu.version=T20
ro.sf.lcd_density=160
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.error.receiver.system.apps=com.acer.android.nidus
acer.sync.adb.mode=ENABLED
ro.setupwizard.mode=DISABLED
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.com.google.clientidbase=android-acer
drm.service.enabled=true
ro.product.modelalias=A100
ro.tether.denied=true
ro.com.google.gmsversion=4.0.3_r0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
+1. A link to which HC to download would be nice!
Possible fix
Just came across this a manual way to put the official update on using the same procedure we used for the leak. Going to give it a try hopefully It doesn't botch my tablet.
http://forum.xda-developers.com/showthread.php?t=1611696
citricube said:
Just came across this a manual way to put the official update on using the same procedure we used for the leak. Going to give it a try hopefully It doesn't botch my tablet.
http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
Ok cool. Tell me how it goes. Im not sure if I wanna try anything because I dont wanna ruin the tablet...its still pretty good with our leak.
Success
In terms of functionality the upgrade went through to the current Official release however my green flickering camera glitch isn't resolved It's either b/c I rooted my tablet or It's just a hardware error -__-
Camera
I was initially still having camera issues even after I patched on the OTA update. However, after a factory reset it seems to be working so far. Going to keep my eye on it and see If the issue comes back as It has many times.
I have two A100 tablets. One is running the latest leaked version of ICS and the other got the OTA update. About Tablet reports the same version for the Image Version and the Build Number on both tablets.
Thanks, sorry about the delay
It was just a hardware issue had it sent into Acer Service Center and they replaced my camera component. I'm not having good luck with my A100 though lol. I pressed the reset button when the tablet was running sluggish the other day and it hung up on the android logo. Tried fixing it and messed it up even more!
hahne said:
I have two A100 tablets. One is running the latest leaked version of ICS and the other got the OTA update. About Tablet reports the same version for the Image Version and the Build Number on both tablets.
Click to expand...
Click to collapse
As many of you know the GSM Note 2 is supported by CyanogenMod in a unified build format. This work is simply monumental with a beautiful product. Many in the T-Mobile Note 2 community are reluctant to use the unified build for a variety of reasons.
Nicktastique and rmanne picked up the mantle and provided us with device specific unofficial CM11 builds. As rmanne has transitioned to a new device, I saw that I would be able to give back to the T889 community and pick up the yoke and keep us moving forward.
My product is no more than a straight source built t0ltetmo build as the CM11 spec is drawn up for the t0ltetmo on the CM github. All source is available at the CM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-CM commits or "fixes" with very few exceptions.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in CM commits that looks promising I expect that I would post a new build.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial CM .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
cm-11-20150322-COUGMADE-t0ltetmo.zip
cm-11-20150313-COUGMADE-t0ltetmo.zip
cm-11-20150222-COUGMADE-t0ltetmo.zip
cm-11-20150206-COUGMADE-t0ltetmo.zip
cm-11-20150116-COUGMADE-t0ltetmo.zip
cm-11-20150107-COUGMADE-t0ltetmo.zip
cm-11-20150101-COUGMADE-t0ltetmo.zip
cm-11-20141220-COUGMADE-t0ltetmo.zip
cm-11-20141216-COUGMADE-t0ltetmo.zip
cm-11-20141212-COUGMADE-t0ltetmo.zip
cm-11-20141209-COUGMADE-t0ltetmo.zip
cm-11-20141206-COUGMADE-t0ltetmo.zip
cm-11-20141201-COUGMADE-t0ltetmo.zip
cm-11-20141126-COUGMADE-t0ltetmo.zip
cm-11-20141027-COUGMADE-t0ltetmo.zip
cm-11-20141020-COUGMADE-t0ltetmo.zip
cm-11-20141011-UNOFFICIAL-t0ltetmo.zip
cm-11-20141002-UNOFFICIAL-t0ltetmo.zip
cm-11-20140921-UNOFFICIAL-t0ltetmo.zip
cm-11-20140914-UNOFFICIAL-t0ltetmo.zip
cm-11-20140906-UNOFFICIAL-t0ltetmo.zip
cm-11-20140831-UNOFFICIAL-t0ltetmo.zip
cm-11-20140826-UNOFFICIAL-t0ltetmo.zip
cm-11-20140818-UNOFFICIAL-t0ltetmo.zip
cm-11-20140810-UNOFFICIAL-t0ltetmo.zip
cm-11-20140806-UNOFFICIAL-t0ltetmo.zip
CyanogenMod Gapps
PA Gapps (good variety of options)
All source code for CyanogenMod is available in the CyanogenMod Github.
CM t0lte git
CM t0ltetmo git
DonkeyCoyote Samsung Vendor git
Props and credit to:
CyanogenMod team (especially t0lte maintainers codeworkx and madmack for their hardwork toward insuring that the Note 2 is kept in the loop).
UtkarshGupta for providing advice in working through build issues on compiling Omni that translated to quick work on CM.
Rmanne for assistance in getting running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.
Mine
Gimme
How is it so far?
Everything seems to be working fine, just as with the unified build, t0lte.
The only thing I was hoping to see in the t0ltetmo build was getting rid of the 'US' as the network provider in the pulldown handle and lockscreen and show T-Mobile instead. Of course I could xpose and change it, but was hoping not to have to do that.
Other than that, the build is solid and bug-free as far as my usage matters.
Thanks for the build, OP!
carlz28 said:
Everything seems to be working fine, just as with the unified build, t0lte.
The only thing I was hoping to see in the t0ltetmo build was getting rid of the 'US' as the network provider in the pulldown handle and lockscreen and show T-Mobile instead. Of course I could xpose and change it, but was hoping not to have to do that.
Other than that, the build is solid and bug-free as far as my usage matters.
Thanks for the build, OP!
Click to expand...
Click to collapse
Yup. The carrier network label has been the bane of my post-build existence. It iritates me too. I figured that someone would mention it on the first page.
Selective-spn-conf.xml doesn't seem to do much for it either. That is my first order of business once I get my other ROM project working (the one I was planning on before rmanne picked up a new device).
nice!
Coug76 said:
Yup. The carrier network label has been the bane of my post-build existence. It iritates me too. I figured that someone would mention it on the first page.
Selective-spn-conf.xml doesn't seem to do much for it either. That is my first order of business once I get my other ROM project working (the one I was planning on before rmanne picked up a new device).
Click to expand...
Click to collapse
No worries! Its one of those OCD things that bugs me on any ROM/device. Wish I could help narrow down the issue but I have no coding/devving/ROM building skills.
2 days running now and no other issues. Definitely a DD build!
New build is up.
Coug76 said:
New build is up.
Click to expand...
Click to collapse
still couldn't figured out how to change the network name?
zain0300 said:
still couldn't figured out how to change the network name?
Click to expand...
Click to collapse
No. I don't have a timeline either. I do this for fun, in my spare time. It may be tomorrow. It may be next month. I am also working on another project as well.
Coug76 said:
No. I don't have a timeline either. I do this for fun, in my spare time. It may be tomorrow. It may be next month. I am also working on another project as well.
Click to expand...
Click to collapse
i never asked when are you gonna fix it
What don't u try to edit build.prop
Sent from my SGH-T889 using XDA Free mobile app
sipher26 said:
What don't u try to edit build.prop
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
What did you get to work? I am hoping to trip over something soon. I have been mucking around in the .conf files for a while now.
I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app
sipher26 said:
I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Here is the build.prop. If you let me know I can try it out as I have a nandroid sitting on my SD card all the time.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84Q
ro.build.display.id=cm_t0ltetmo-userdebug 4.4.4 KTU84Q bd05cc81b5 test-keys
ro.build.version.incremental=bd05cc81b5
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Sat Aug 9 22:04:17 PDT 2014
ro.build.date.utc=1407647057
ro.build.type=userdebug
ro.build.user=cougatron
ro.build.host=cougatron-MS-7793
ro.build.tags=test-keys
ro.product.brand=samsung
ro.product.name=t0ltetmo
ro.product.board=smdk4x12
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=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=t0ltetmo
ro.product.model=SGH-T889
ro.product.device=t0ltetmo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=t0ltetmo-user 4.1.2 JZO54K T889UVBMB4 release-keys
ro.build.fingerprint=samsung/t0ltetmo/t0ltetmo:4.1.2/JZO54K/T889UVBMB4:user/release-keys
ro.build.characteristics=default
ro.cm.device=t0ltetmo
# end build properties
#
# from device/samsung/t0ltetmo/system.prop
#
#
# system.prop for t0ltetmo
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/ttyS0
ro.telephony.default_network=9
telephony.lteOnGsmDevice=1
ro.sf.lcd_density=320
ro.lcd_min_brightness=20
# System property ril adb log on
persist.radio.adb_log_on=1
# For sys info indication
persist.radio.add_power_save=1
# System property for SIM
persist.radio.apm_sim_not_pwdn=1
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-tmobile-us
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
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.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.dalvik.multithread=false
persist.sys.dun.override=0
persist.sys.root_access=1
ro.cm.version=11-20140810-UNOFFICIAL-t0ltetmo
ro.cm.releasetype=UNOFFICIAL
ro.modversion=11-20140810-UNOFFICIAL-t0ltetmo
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
persist.sys.recovery_update=false
ro.cm.display.version=11-20140810-UNOFFICIAL-t0ltetmo
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.ringtone=Orion.ogg
ro.carrier=unknown
ro.telephony.ril_class=SamsungQualcommRIL
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.zygote.disable_gl_preload=1
ro.opengles.version=131072
ro.bq.gpu_to_cpu_unsupported=1
debug.hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
persist.sys.dalvik.vm.lib=libdvm.so
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
sipher26 said:
I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Any luck?
New build up.
looks to me that it is showing your region.local instead of your service provider
mattlowry said:
looks to me that it is showing your region.local instead of your service provider
Click to expand...
Click to collapse
I'm trying to figure out how to fix it and am getting frustrated with it. That same behavior is present in the official builds of CM and Omni. I have been digging through the source git for AOKP to see if I can tell how they are making it work. I can only work on it after the kids are in bed but before I sleep. My eyes are starting to cross...