Related
I9000M_JK5_JK5_JK5_JK5_UG_BMC (Mislabeled, actually JK3)
ro.build.date = 2010.11.18 00:13:25 KST
ro.build.fingerprint = samsung/GT-I9000M/GT-I9000M/GT-I9000M:2.2/FROYO/UGJK3:user/release-keys
http://www.multiupload.com/WTVA1P5NEX
NOTICE: I do not have this device model, nor have I tested the ROM, I'm only telling you where to find it.
can anyone give me info on this rom
english etc
After i installed my ARHD on my DHD i have problems with GPS. It's not as accurate as it was with stock ROM, please help !
I've had my DHD for less than a year and also started getting gps issues (long time to fix, low accuracy, only 3 to 4 sats). After trying many roms and many software hacks (gps.conf to gps-status etc.) I started looking at hardware. I noticed that the connections in my gps-antenna cover were wearing out. I ordered a new gps-antenna and replaced it and now it works great again.
Check the post in my sig for a video how to change the gps-antenna (not my video)
we don't have the same problem, when i'm at home my gps shows that i'm in completely different city, but when i'm in the citymall for example it shows correctly...
GPS problem
Hi wrooney, you're not using Google maps 6.03 are you? Coz I had real problems with that and ARHD almost impossible to get a fix. They have updated maps to 6.10 now and that's working fine in my DHD with ARHD 6.31.
i have Maps version 6.0.1 and android revolution HD 6.3.1, now what should i do? somehow manually update maps?
Have you tried AGPS?
http://forum.xda-developers.com/showthread.php?t=1252011
I've been getting upwards of 8 sats and consistency connecting and locking on very quickly. I don't "activate" my GPS until I'm outside or in my car. It seems that helps a ton. I always open up GPS Toolbox before I route as well, so it can download some daily data.
Because at home you can't get GPS
Except if you leave in a tent of course...
Your phone is using 3 localization info: Wifi, GPS and cell towers.
I had exactly the same problem with Celcom in MY.
At home, perfect cell localization.
But in my office I was 50km away.
Wrong configuration of the tower.
To be sure, activate only one of the 3 (WiFi, GPS or data). I think switch of wifi and data as I bet on tower pb. You can also modify this in 'localization config'
Edit: in China, sometime the phone says it's locked on GPS but it put me at more than 50km away.
To solve it I activate data before launching Maps.
As stated before, GPS Status is a good to tool to check the GPS lock. Don't mess to much with pseudo soft to improve GPS... for me it's bul**t.
Good config of gps.conf is enough.
i post them for you as an example. But you have to adapt it for your country, this one is for China.
my gps.conf (zipped for upload)
but you don't get my problem my gps was working perfectly until i installed ARHD
I get your problem... but are you sure you kept the exact same config after flash?
Before I flash a ROM I always replace gps.conf in the zip by the one I attached for ex. I do the same with Maps.apk.
Are you sure that the config of localisation has not been modified between your previous ROM and this one? Are you sure to use the same version of the soft you're using for GPS? Same config of A-GPS.
By flashing the ROM you didn't change the HW and the radio. So the GPS reception has to be the same, only the way data is used is different now.
And last but not least... I can be wrong also. It's just my ideas and problems I encountered.
i don't know how to change the gps.conf, but i would like to try upg maps to lates version first than trying other methods, do you know how can i do that?
Thanks man the GPS.config file fixed my GPS problem
Sent from my Desire HD using xda premium
GPS probs
Attached a copy of Google maps 6.10. And GPS status which should help with fix speed.
i installed google maps and gpsstatus, but still innacuratte... :S
wrooney10 said:
i don't know how to change the gps.conf, but i would like to try upg maps to lates version first than trying other methods, do you know how can i do that?
Click to expand...
Click to collapse
Sorry.. to change gps.conf, just use rootexplorer (or equivalent) and replace the one you have in /system/etc/ (copy paste).
To upgrade maps is more tricky. On some ROM I can't... that's why I replace it before flashing (open the zip with 7zip and replace maps.apk in /system/apps/ with the one you want).
As I get use to it, I always replace these two files in a zip before flashing a rom (+delete apks I don't want, remove all ringtones and notif sounds...). It's easier to tune the zip than doing one by one on the phone.
i have the same problems with the RCMix3d Runny v4.0 i also used the patch of iBotPeaches but it dosen't work. i check the build.prop file and thereisn't anything about the gps, it's normal?
this is my build.prop file, it's normal? i need to write something?
#Edited by JSLEnterprises for RCMIX
ro.ril.ecc.VODA-Africa-South=112,999,911
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-Dutch=112
ro.ril.ecc.HTC-FRA=112,911
ro.ril.ecc.HTC-ITA=112,911
ro.ril.ecc.HTC-EastEurope=911
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.amr.wb.HTC__A07=1
ro.phone.min_match.HTC__Y13=7
ro.ril.enable.amr.wb.HTC__Y13=1
ro.ril.enable.amr.wb.HTC__E11=1
ro.ril.enable.amr.wb.HTC__001=1
ro.phone.min_match.HTC__J15=7
ro.phone.min_match.HTC__016=7
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420
ro.ril.enable.sdr=1
ro.ril.enable.amr.wideband=1
ro.com.google.clientidbase=android-htc-rev
ro.ril.vmail.23415=1571,BT
ro.ril.vmail.27203=171
ro.ril.vmail.65502=181
ro.ril.vmail.27211=171
ro.config.htc.enableCOTA=1
# begin build properties
# autogenerated by buildinfo.sh
ro.aa.customizationid=253838
ro.aa.project=Runnymede
ro.aa.romver=1.05.401.4
ro.aa.maincid=HTC__001
ro.aa.cidlist=HTC__001,HTC__E11,HTC__203,HTC__102,HTC__405,HTC__Y13,HTC__A07,HTC__304,HTC__032,HTC__N34,HTC__J15,HTC__016
ro.aa.skulist=401
ro.aa.rid=313
ro.aa.modelid=PD9810000
ro.build.changelist=185058
ro.aa.taskid=221900
ro.aa.mainsku=401
ro.cwkey=HTC__001
ro.com.google.clientidbase=android-htc
ro.aa.customizationid=253838
ro.build.id=GRJ90
ro.build.display.id=GRJ90
ro.build.version.incremental=182513.4
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=三 10月 19 12:08:18 CST 2011
ro.build.date.utc=1318997298
ro.build.type=user
ro.build.user=
ro.build.host=ABM012
ro.build.tags=release-keys
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=runnymede
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=1.05.401.4 CL185058 release-keys
ro.product.ua=
ro.build.fingerprint=htc_europe/htc_runnymede/runnymede:2.3.5/GRJ90/182513.4:user/release-keys
ro.build.project=Runnymede:221900
ro.product.version=RCMix3D Runny v4.0
ro.build.languageremove=0
ro.build.sense.version=3.5
keyguard.no_require_sim=1
# end build properties
#
# system.prop for mahimahi
#
ro.sf.lcd_density=240
debug.fb.rgb565 = 0
# Use GPU for rendering UI
debug.sf.hw=1
rild.libpath=/system/lib/libhtc_ril.so
# Modify MMS APN retry timer from 5s to 2s.
ro.gsm.2nd_data_retry_config = max_retries=3, 2000, 2000, 2000
# ace RF team request
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 12
ro.ril.hsdpa.category = 10
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 2
# Default network type.
# 0 => WCDMA mode preferred.
ro.telephony.default_network = 0
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=8
wifi.interface=eth0
wifi.supplicant_scan_interval=30
# 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
# For the default value of agps
ro.ril.def.agps.mode = 1
# For HSDPA low throughput
ro.ril.disable.power.collapse = 1
# For FOTA setting (leave empty value to use default)
ro.htc.checkin.url = i can't post the url, if you need it write me a pm
ro.htc.checkin.crashurl = i can't post the url, if you need it write me a pm
ro.htc.checkin.url_CN = i can't post the url, if you need it write me a pm
ro.htc.checkin.crashurl_CN = i can't post the url, if you need it write me a pm
ro.htc.checkin.exmsg.url = i can't post the url, if you need it write me a pm
ro.htc.checkin.exmsg.url_CN = i can't post the url, if you need it write me a pm
ro.htc.appupdate.url = i can't post the url, if you need it write me a pm
ro.htc.appupdate.url_CN = i can't post the url, if you need it write me a pm
ro.htc.appupdate.exmsg.url = i can't post the url, if you need it write me a pm
ro.htc.appupdate.exmsg.url_CN = i can't post the url, if you need it write me a pm
# Release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.50.032
#0x10000010010100100000011 represent bt profile list
ro.bt.profiles = 4270339
# enable data roaming
ro.com.android.dataroaming = true
# Properties of BTLA stack
service.brcm.bt.activation = 0
service.brcm.bt.srv_active = 0
service.brcm.bt.hcid_active = 0
service.brcm.bt.btld = 0
service.brcm.bt.btld_pid = 0
service.brcm.bt.avrcp_pass_thru = 0
service.brcm.bt.avrcp_toggle = 1
service.brcm.bt.local_name =
# For quick boot mode
persist.sys.shutdown.mode = hibernate
# Vivo China NEL use
ro.ril.update.vivo.acoustic = 1
# Properties of Scalado Denoise param.
postprocess.iso_midband = 400
postprocess.denoise_level = 5
# Following property will be reference by Settings.
ro.product.processor= 1GHz Qualcomm Snapdragon 8255
ro.product.ram= 768MB
ro.product.display_resolution= 4.3" WVGA Screen
ro.product.main_camera= 8 Megapixel
ro.product.front_camera= NA
ro.product.bluetooth= 3.0
ro.product.wifi = 802.11 B/G/N
# For opensense sdk
ro.htc.common.version = 2.1.0.0
# For ext4 file system
ro.ext4fs = 1
# Dump native call stack when an ANR happens to com.htc.launcher.
profiler.anr_dump_native_uid = 9999
# Enable egl profiler
debug.egl.profiler = 1
# Properties for supporting framework features
ro.htc.framework.screencapture = true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal= i can't post the url, if you need it write me a pm
ro.url.legal.android_privacy= i can't post the url, if you need it write me a pm
ro.com.google.networklocation=1
ro.setupwizard.mode=DISABLED
ro.setupwizard.mode=OPTIONAL
ro.config.ringtone=QuietlyBrilliant.mp3
ro.config.notification_sound=Zeta.mp3
ro.config.alarm_alert=NewDay.mp3
ro.config.cal_notification=Epsilon.mp3
ro.config.msg_notification=Gamma.mp3
ro.setupwizard.mode=DISABLD
ro.com.google.gmsversion=2.3_r7
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.hac.enable=1
ro.setupwizard.enterprise_mode=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.adb.notify=0
windowsmgr.max_events_per_sec=120
ro.rommanager.developerid=capychimp
ro.modversion=RCMix3D Runny 4.0
Click to expand...
Click to collapse
swazii said:
Thanks man the GPS.config file fixed my GPS problem
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Did you modify the conf in any way with your country and continent or did you leave it the way it was?
i'm trying to port the Evo 3D stock unrooted rom to our Evo 4g and i wanted to know what are some edits i have to do to the build prop?
i wasn't sure which dev to PM about this but i was hoping if someone isnt too busy and is on this sub-forum, maybe could help :good:
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-sprint-us
ro.com.google.clientidbase.am=android-sprint-us
ro.com.google.clientidbase.ms=android-sprint-us
ro.phone.min_match=7
ro.product.model=PG86100
service.htc.bt.local_name=HTC EVO 3D
ro.cdma.home.operator.alpha=sprint
gsm.sim.operator.alpha=sprint
gsm.operator.alpha=sprint
ro.cdma.home.operator.numeric=310120
gsm.sim.operator.numeric=310120
gsm.operator.numeric=310120
gsm.sim.operator.iso-country=us
gsm.operator.iso-country=us
ro.net.apnwhitelist=admin
ro.htc.checkin.delay=0
ro.da1.enable=true
# begin build properties
# autogenerated by buildinfo.sh
ro.aa.customizationid=392393
ro.aa.project=Shooter_ICS_35_S
ro.aa.romver=2.89.651.2
ro.aa.maincid=SPCS_001
ro.aa.cidlist=SPCS_001
ro.aa.rid=125
ro.aa.modelid=PG8610000
ro.aa.report=com
ro.build.display.id=2.89.651.2 710RD
ro.aa.skulist=651
ro.product.brand=sprint
ro.product.model=PG86100
ro.aa.mainsku=651
ro.onecid=
ro.cwkey=SPCS_001
ro.aa.taskid=271053
ro.com.google.clientidbase=android-sprint-us
ro.build.id=IML74K
ro.build.display.id=IML74K
ro.build.version.incremental=409645.2
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=五 7月 6 19:06:40 CST 2012
ro.build.date.utc=1341572800
ro.build.type=user
ro.build.user=
ro.build.host=ABM011
ro.build.tags=release-keys
ro.product.model=PG86100
ro.product.brand=sprint
ro.product.name=htc_shooter
ro.product.device=shooter
ro.product.board=shooter
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shooter
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=2.89.651.2 CL409645 release-keys
ro.build.description=2.89.651.2 CL409645 release-keys
ro.build.changelist=409645
ro.build.fingerprint=sprint/htc_shooter/shooter:4.0.3/IML74K/409645.2:user/release-keys
ro.build.characteristics=default
ro.build.project=Shooter_ICS_35_S:271053
ro.product.version=2.89.651.2 710RD
ro.build.languageremove=0
ro.build.sense.version=3.5
keyguard.no_require_sim=1
# end build properties
#
# system.prop for shooter
#
ro.sf.lcd_density=240
sf.debug.enable3D = 1
debug.fb.rgb565 = 0
debug.sf.hw = 1
debug.composition.type = c2d
debug.enabletr = true
debug.qctwa.preservebuf = 1
rild.libpath=/system/lib/libhtc_ril.so
# Default network type.
# 4 => CDMA mode preferred.
ro.telephony.default_network=4
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=8
persist.data_netmgrd_mtu=1472
#
wifi.interface=wlan0
wifi.supplicant_scan_interval=90
# 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.
# Change to 32m, due to 2.3.3 GB already change to 32m
# For ICS project, default 32m/48m
dalvik.vm.heapsize=128m
dalvik.vm.heapgrowthlimit=48m
# For the default value of agps
ro.ril.def.agps.mode = 2
# For emmc phone storage
ro.phone_storage = 0
# For ext4 file system
ro.ext4fs = 1
# For FOTA setting (leave empty value to use default)
ro.htc.checkin.url = http://andchin.htc.com/android/checkin
ro.htc.checkin.crashurl = http://andchin.htc.com/android/crash
ro.htc.checkin.url_CN = http://andchin.htccomm.com.cn/android/checkin
ro.htc.checkin.crashurl_CN = http://andchin.htccomm.com.cn/android/crash
ro.htc.checkin.exmsg.url = http://fotamsg.htc.com/android/extra/
ro.htc.checkin.exmsg.url_CN = http://fotamsg.htccomm.com.cn/android/extra/
ro.htc.appupdate.url = http://apu-chin.htc.com/check-in/rws/and-app/update
ro.htc.appupdate.url_CN = http://apu-chin.htccomm.com.cn/check-in/rws/and-app/update
ro.htc.appupdate.exmsg.url = http://apu-msg.htc.com/extra-msg/rws/and-app/msg
ro.htc.appupdate.exmsg.url_CN = http://apu-msg.htccomm.com.cn/extra-msg/rws/and-app/msg
# release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.50.032
#0x10000010010100101000011 represent bt profile list
ro.bt.profiles = 4270403
# Properties of BTLA stack
service.brcm.bt.activation = 0
service.brcm.bt.srv_active = 0
service.brcm.bt.hcid_active = 0
service.brcm.bt.btld = 0
service.brcm.bt.btld_pid = 0
service.brcm.bt.avrcp_pass_thru = 0
service.brcm.bt.avrcp_toggle = 1
service.brcm.bt.local_name =
#Welly_Fang
ro.htc.device.slot1 = NV
# Following property will be reference by Settings.
ro.product.processor = 1.2 GHz dual core
ro.product.ram = 1GB
ro.product.display_resolution = 4.3 inch qHD resolution
ro.product.main_camera = 5M * 2
ro.product.front_camera = 1.3M
ro.product.bluetooth = 3.0
ro.product.wifi = 802.11 b/g/n
# For opensense sdk
ro.htc.common.version = 3.0.0.0
# Properties for supporting framework features
ro.htc.framework.screencapture = true
# For QC perf binary hooks
# src:vendor/qcom/proprietary/android-perf/release/lib/<CPU arch>/libqc-opt.so
ro.vendor.extension_library=/system/lib/libqc-opt.so
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.setupwizard.mode=OPTIONAL
ro.config.ringtone=QuietlyBrilliant.mp3
ro.config.notification_sound=Zeta.mp3
ro.config.alarm_alert=NewDay.mp3
ro.config.cal_notification=Epsilon.mp3
ro.config.msg_notification=Gamma.mp3
drm.service.enabled=true
ro.com.google.gmsversion=4.0_r2
ro.da1.enable=true
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.hac.enable=1
lpa.decode=true
lpa.use-stagefright=true
htc.audio.q6.topology=0
ro.setupwizard.enterprise_mode=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Just search for a rom porting tutorial, using a rom with a different processor and resolution is gonna take a lot more work than editing the build.prop and copying the files over, may wanna try using a shooter based rom and removing su and busybox to unroot it
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
-EViL-KoNCEPTz- said:
Just search for a rom porting tutorial, using a rom with a different processor and resolution is gonna take a lot more work than editing the build.prop and copying the files over, may wanna try using a shooter based rom and removing su and busybox to unroot it
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Click to expand...
Click to collapse
thanks, im using a this Guide hoping it would work. im new to this.
when you say base, what do you mean? i'm using the latest stock OTA from the shooter
alexandroid5 said:
thanks, im using a this Guide hoping it would work. im new to this.
when you say base, what do you mean? i'm using the latest stock OTA from the shooter
Click to expand...
Click to collapse
When you port a rom you have 2 roms you're working with a base and the one you're porting, to make it simple its best to use 2 roms that have the same screen resolution and same processor type. The evo is a single core processor , hdpi resolution and the 3d is a dual core processor xhdpi or qhd resolution. When working with these 2 to make a port any graphics and ui elements from the shooter need to be resized to fit the supersonic screen properly, and changes need to be made in alot of the system files for the rom to use the processor right. For someone with little to no experience doing a port and due to time it would be easier and quicker to find a stockish shooter rom already ported to the evo and remove root, otherwise you will be spending weeks resizing graphics and learning what need to be modded for the processor to work right. Most 3d ports take around 2 wweeks to a month depending on the time per day modifying the graphics and system files mostly cuz there's is just so much go modify and its time consuming. However stripping root should take no more than a few hours depending on your knowledge level, I could probably remove root in about 10 minutes cuz I know what files to look for to delete and where to look for them. If you want to learn to port roms id suggest starting with 2 roms with the same resolution and chipset for your first few tries and then expanding from there as your comfort level improves and you are successfully making booting ports the flash with no errors.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
-EViL-KoNCEPTz- said:
When you port a rom you have 2 roms you're working with a base and the one you're porting, to make it simple its best to use 2 roms that have the same screen resolution and same processor type. The evo is a single core processor , hdpi resolution and the 3d is a dual core processor xhdpi or qhd resolution. When working with these 2 to make a port any graphics and ui elements from the shooter need to be resized to fit the supersonic screen properly, and changes need to be made in alot of the system files for the rom to use the processor right. For someone with little to no experience doing a port and due to time it would be easier and quicker to find a stockish shooter rom already ported to the evo and remove root, otherwise you will be spending weeks resizing graphics and learning what need to be modded for the processor to work right. Most 3d ports take around 2 wweeks to a month depending on the time per day modifying the graphics and system files mostly cuz there's is just so much go modify and its time consuming. However stripping root should take no more than a few hours depending on your knowledge level, I could probably remove root in about 10 minutes cuz I know what files to look for to delete and where to look for them. If you want to learn to port roms id suggest starting with 2 roms with the same resolution and chipset for your first few tries and then expanding from there as your comfort level improves and you are successfully making booting ports the flash with no errors.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Click to expand...
Click to collapse
wow this explained alot. THANKS A LOT!! Is there any links you could post for me to start developing in general (not just porting)
Z
alexandroid5 said:
wow this explained alot. THANKS A LOT!! Is there any links you could post for me to start developing in general (not just porting)
Click to expand...
Click to collapse
I would recommend starting with tommytomatoes tutorial and reading I'm chef central on the forums I think its up near Android general on the main forum page, I'm on tapatalk right now so I'm not sure exactly where its located but ill go grab a link in a sec
Edit: from main forum page its chef central > android it wouldn't let me grab a link to the entire forum but you should be able to find it once you get to the main forum page where all the device links are located
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
---------- Post added at 02:37 AM ---------- Previous post was at 02:32 AM ----------
For a beginner I suggest starting with just a few tools like dsixda kitchen, tommytomoatoes android utility and gimp for editing graphics unless you already have Photoshop, gimp is free and does everything Photoshop will do you just have to download plugins and brushes to beef it up from the base install, deviant art has alot of brushes you can download and the gimp repository has alot of plugins you can pick and install
Edit: also learning to use Linux (Ubuntu, opensuse, mint which even you choose) will help if and when you decide to dive deeper and start working with source to compile roms and build from raw source, notepad++ is also a must for editing the source code in decompiled apks and updater binaries.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
-EViL-KoNCEPTz- said:
Z
I would recommend starting with tommytomatoes tutorial and reading I'm chef central on the forums I think its up near Android general on the main forum page, I'm on tapatalk right now so I'm not sure exactly where its located but ill go grab a link in a sec
Edit: from main forum page its chef central > android it wouldn't let me grab a link to the entire forum but you should be able to find it once you get to the main forum page where all the device links are located
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
---------- Post added at 02:37 AM ---------- Previous post was at 02:32 AM ----------
For a beginner I suggest starting with just a few tools like dsixda kitchen, tommytomoatoes android utility and gimp for editing graphics unless you already have Photoshop, gimp is free and does everything Photoshop will do you just have to download plugins and brushes to beef it up from the base install, deviant art has alot of brushes you can download and the gimp repository has alot of plugins you can pick and install
Edit: also learning to use Linux (Ubuntu, opensuse, mint which even you choose) will help if and when you decide to dive deeper and start working with source to compile roms and build from raw source, notepad++ is also a must for editing the source code in decompiled apks and updater binaries.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Click to expand...
Click to collapse
Thank you! I already have photoshop, DSIXDA kitchen and notepad++
so far i have only de-odex roms, themed with the online kitchen, and messed a little with the build.prop to increase image quality and basic stuff like that but i do want to learn more than just that. i plan on majoring in computer science (im starting as a freshman in college this fall) but i want to get ahead and learn as much as i can
Hello,
I do not know who is the manufacturer of my device (I bought the car with the device and I still could not identify it), it seems to be a copy, the configuration of the buttons looks like the one from Witson, but It's not exactly the same.
Model number: S07
S / N: 000000000000000
MCU version: MTCB-KYD-V2.77
Build number: rk3188-eng4.4.4 27082015.10: 37: 37
Kernel: 3.0.36+ root @ chun # 187
The problems I'm facing:
- Bluetooth - finds no devices, I tried all the variants of boards in the factory settings
- WiFi - does not start, it's turning on and then turns back to off
- USB - does not work
I opened it to see if something was fried or loose, but after a visual inspection I did not see anything special. The board is:
Model: KYD-3000 MB
Release: ver2.0
Board: FR4 1.2mm
Date: 2014-11-08
I saw on https://forum.xda-developers.com/android-auto/mtcb-android-head-units-qa/wifi-usb-t3492377 that there is a wifi + USB solution for KLD2. Does it apply to KYD?
Can you help me with any suggestions?
tx
rom custom for 2din chinese radio please?
hello I have a china radio with firmware
2016-12-06--12-55-55_astar_y3-eng_4.4.2_KVT49L_20160129_test-keys
and I would like to know if it is possible to put a custom rom on my radio please?
thank you very much for your help please
You must see the MCU version to see which is the brand of your HU. In the info from the MCU version you have xxxx_ name of the maker_Version.
With the maker's name you can look for the correct update image for your unit.
hello Ovarb
I only have this as info:
Details:
ro.product.model = QuadCore-R16
ro.product.brand = TW
ro.product.name = astar_y3
ro.product.device = astar-y3
ro.product.board = exdroid
ro.product.cpu.abi = armeabi-v7a
ro.product.cpu.abi2 = armeabi
ro.product.manufacturer = tw
ro.product.firmware = v2.0
its good ?
here is the rest
Processor Type = Quadcore-R16 1.6G
Android version = 4.4.2
MCU Version = 5.3.18-23-B02-E43101-160531
System Version = 4.5.10_20160618
Sorry but the information you put doesn't help me in identifying what rom you've got.
Hello ,
I have to remove my radio to see
and in the back it is noted PENGHUI
MODEL: DABC-5993 RV / 16
this is all I have as information
I do not know anything to give you more
Si alguen sabe de una rom personalizada aquí esta la información de ma mia