First of all thanks for the developers who atleast took a look at our device
It is really hard to say that i can't go further.I have tried everything upto my level but the fact is we don't have the proper resources and after all we are having a low end samsung phone which means aftermarket development is nearly impossible.
But i still hope someday this device going to see it's dawn.we have to wait for that.
Thanks for everyone who supported me on this fix.
sambathpkr said:
hello guys,
for the past two weeks i'm trying to fix the ril in psych_half's cyanogenmod 10.1 buid.he already told that trying to fix ril causes com.android.phone has stopped working and crashes the entire system.later i found out that this problem is mainly because of the line added in the build.prop for telephony.
"ro.telephony.ril_class="
the ril class name should be as that of the Ril hardware used in our device.because of the spreadtrum chip used in our device many people cant figure out the ril_class name.giving wrong name force closes the telephony.eventhough i have done a lot of research in internet i couldn't find the ril_class.yesterday by interpretting several logcats i found out the ril class name as follows
'ro.telephony.ril_class=RIL":good:
sounds weird..!!???but it works.so phone force close fixed:good:
by adding these lines in build.prop
in SYSTEM PROPERTIES
ro.telephony.ril_class=RIL
rild.libpath=/system/lib/libreference-ril.so
in ADDITIONAL PROPERTIES
persist.sys.sprd.modemreset=0
and adding these files from stock rom's /system/bin to cm's /system/bin
modemd
dttexe
engmodemclient
engappclient
engpccclient
engservice
by adding these things nearly fixes the ril.once i got my carrier name on the lockscreen once.but i dont know how it happened.
the main problem seen in the logcat is everything working fine except the radio turning off suddenly.even the ril connects to the socket.
i'm attaching the logcat below.looking forward to fix ril.
developers take a look at this logcat and give us some suggestions
i've also tried to manually turn on the radio by dialing *#*#4636#*#*.but some time it works but sometimes not
so dont loose hope on this little device.little bit of hardwork required.
Click to expand...
Click to collapse
Excellent We are quite close to a revolution....
Pls tell me if u hv anything u want me to look up (since i cant do the things u do in linux)
I hv not been able to contact @psych.half
may be he can fix now tht u once got the ril working hmm ?
T3snake said:
Excellent We are quite close to a revolution....
Pls tell me if u hv anything u want me to look up (since i cant do the things u do in linux)
I hv not been able to contact @psych.half
may be he can fix now tht u once got the ril working hmm ?
Click to expand...
Click to collapse
yeah I've also tried to contact him but he is not available.I think he disabled his account .
I'm trying with my best..everything works fine in the logcat except the radio turning off suddenly.we have to find a workaround for that.
tag cm developers ..mm so that we can find a clue or they may help us?
By the way awesome work dude ...happy to see someone still working on this device ..best of luck
Bro you do awesome job
Sent from my GT-S5282 using Tapatalk
---------- Post added at 11:27 AM ---------- Previous post was at 11:26 AM ----------
Ill try to do build.prop edit but no one guide me
Sent from my GT-S5282 using Tapatalk
sambathpkr said:
hello guys,
for the past two weeks i'm trying to fix the ril in psych_half's cyanogenmod 10.1 buid.he already told that trying to fix ril causes com.android.phone has stopped working and crashes the entire system.later i found out that this problem is mainly because of the line added in the build.prop for telephony.
"ro.telephony.ril_class="
the ril class name should be as that of the Ril hardware used in our device.because of the spreadtrum chip used in our device many people cant figure out the ril_class name.giving wrong name force closes the telephony.eventhough i have done a lot of research in internet i couldn't find the ril_class.yesterday by interpretting several logcats i found out the ril class name as follows
'ro.telephony.ril_class=RIL":good:
sounds weird..!!???but it works.so phone force close fixed:good:
by adding these lines in build.prop
in SYSTEM PROPERTIES
ro.telephony.ril_class=RIL
rild.libpath=/system/lib/libreference-ril.so
in ADDITIONAL PROPERTIES
persist.sys.sprd.modemreset=0
and adding these files from stock rom's /system/bin to cm's /system/bin
modemd
dttexe
engmodemclient
engappclient
engpccclient
engservice
by adding these things nearly fixes the ril.once i got my carrier name on the lockscreen once.but i dont know how it happened.
the main problem seen in the logcat is everything working fine except the radio turning off suddenly.even the ril connects to the socket.
i'm attaching the logcat below.looking forward to fix ril.
developers take a look at this logcat and give us some suggestions
i've also tried to manually turn on the radio by dialing *#*#4636#*#*.but some time it works but sometimes not
so dont loose hope on this little device.little bit of hardwork required.
Click to expand...
Click to collapse
try replacing rild with the stock roms rild
jerin jose said:
try replacing rild with the stock roms rild
Click to expand...
Click to collapse
that not working(ppl hv tried but u just cant do that)
Can you give screenshot of carrier showing ?
Sent from my GT-S5282 using Tapatalk
akshaygalaxystarmod said:
Can you give screenshot of carrier showing ?
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
I told I got it once..but I dont know how that happened.
Okay
Sent from my GT-S5282 using Tapatalk
friends please ask help from various developers you know or you don't know.I know that most of the developers not respond for our request.but some one may be interested.find that some one.but do not spam their inbox.ask help from them through pm once if they are ok then they will reply for our pm.if they are not replying leave it.I don't know what happened [email protected]_half if he is there it'll be helpful
while asking help mention this post and ask to take a look at this logcat.I've started to ask..u guys also try.
@sambathpkr
The rild.libpath uses libsec-ril.so and also make sure you use the correct rild file(in the bin folder)!
v_superuser said:
@sambathpkr
The rild.libpath uses libsec-ril.so and also make sure you use the correct rild file(in the bin folder)!
Click to expand...
Click to collapse
thanks for ur suggestion
but our phone uses spreadtrum chip,
we are not having libsecril-so,
and we are using the correct rild file named rild_sp
or the libsecril.so is present somewhere else except /system/lib.
and we are using files from stock
T3snake said:
that not working(ppl hv tried but u just cant do that)
Click to expand...
Click to collapse
look at this error
Code:
D/RIL ( 107): onRequest: OEM_HOOK_RAW sState=1
D/RIL ( 107): RIL_REQUEST_OEM_HOOK_RAW: data[0]=12
D/RIL ( 107): RIL_REQUEST_OEM_HOOK_RAW: data[1]=e
D/RIL ( 107): RIL_REQUEST_OEM_HOOK_RAW: data[2]=0
D/RIL ( 107): RIL_REQUEST_OEM_HOOK_RAW: data[3]=4
D/RIL ( 107): else RIL_REQUEST_OEM_HOOK_RAW
E/RILC ( 107): RIL_onRequestComplete: invalid RIL_Token
D/RIL_ATD ( 108): SetAtdStatus(), 1_0_0
D/RIL_ATD ( 108): SERIALNO: R21D5409GER
D/RIL_ATD ( 108): ril.serialnumber: R21D5409GER
D/RIL_ATD ( 108): ListenFD()
its all abt rild i guess
---------- Post added at 01:52 PM ---------- Previous post was at 01:38 PM ----------
I am not talking abt rild_sp .I am talking abt rild but it is not there in the stock rom
how u r certain that is because of rild.I can't find any clue on your log...??
sambathpkr said:
how u r certain that is because of rild.I can't find any clue on your log...??
Click to expand...
Click to collapse
i did sm research work bro
any progress?
ask
is there no any other problems than the radio?
booompannnes! said:
is there no any other problems than the radio?
Click to expand...
Click to collapse
camera and radio thats all
Sent from my GT-S5282 using Tapatalk
booompannnes! said:
is there no any other problems than the radio?
Click to expand...
Click to collapse
T3snake said:
camera and radio thats all
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
Another problem you forgot it ...microphone not working I tried to record some things it didn't worked and to be sure I tried talking jenjer app but I get message error "can't open microphone ".. .
Related
I have been trying to get service on the .368 or .42 or .62 firmware. So far I have only been able to boot the systems and play around with the apps and settings. I made a backup of each system and am sharing them here so that other r800x users can flash and mess around with the newer systems and that maybe someone smarter then me can figure out, if even possible, how we can get service on these systems as the cdma patch does not work on these. You will be able to use most of everything minus having no service what so ever.
Below are the links to each backup, Before flashing please make a backup of your current system if you dont have one already. All of these will boot with "Unknown Baseband" and "No Service"
Please read everyting before you install any of these
4.0.A.2.368 (2.3.3)
http://www.mediafire.com/?u04dbhea359gm8w
The [.368] R800x backup was made while on the .368 DoomKernel which you will find here http://forum.xda-developers.com/showpost.php?p=16291835&postcount=3
You will want to use the same kernel or you wont have any hardware buttons
4.0.2.A.0.42 (2.3.4)
http://www.mediafire.com/?ic33qd61ck39up6
4.0.2.A.0.62 (2.3.4)
http://www.mediafire.com/?idihgb2hdn928hf
EDIT : Will update backups
The [.42] and [.62] R800x Backups were made using the "Testing" CDMA DoomKernel V10 which you will find here http://forum.xda-developers.com/showpost.php?p=21948440&postcount=126
~You will want to use the same Kernels as I did or you may not have any hardware buttons~
Maybe someone can help with this part, the cdma patch is already known not to work on these systems, So I decompiled the SemcPhone.apk from the cdma patch zip file and compared all the smali files in smali folder to all the smali files in the [.62] decompiled smali folder I found some differences and I am posting a zip file of:
-all the smali files that were IN the cdma patch smali folder that were not in the [.62] smali folder
-a List of smali files that the [.62] smali folder HAD that the cdma patch smali folder did NOT have.
- the [.62] AndroidManifest.xml because it to had differences
The zip of differences can be found here http://www.mediafire.com/?kuv8x82vhthgp9c
Also Im posting a zip file containing the lib files from the 2.3.3 Verizon system which should be our Baseband files ( I could be wrong on which files are the baseband from our r800x), that can be found here http://www.mediafire.com/?afx0unj80ne1r2z
This is basically where I am at with getting service on newer Uk firmware for our r800x, I would gladly love anyones input and/or ideas. If Im wasting my time and someone who knows more then me already knows this wont ever work please let me know! I hope I made everything clear on what it all is and what Im trying to do, thanks for reading and any insight on service
I'm looking forward to seeing the progress that you'll make here. I hope you can find a working resolution.
Me too, I dont know much about the breakdown of ROMs but I will cross my fingers and think happy thoughts.
I have an ignorant question: what keeps you from flashing only the verizon baseband after flashing these other firmwares?
crono141 said:
I have an ignorant question: what keeps you from flashing only the verizon baseband after flashing these other firmwares?
Click to expand...
Click to collapse
I already tried, I flashed only the baseband from the 2.3.3 verizon ftf and copied over the 2.3.3 lib files manually aswell. Still says "unknown baseband" Did I do anything wrong?
Sent from my Droid using xda premium
Ah, porting a rom from one model to the other is especially a ***** when they have a different baseband. I attempted it myself once, but I failed miserably...
Good luck with this btw, I hope you get somewhere with it
Keiran
Any luck getting it to work?
KeiranFTW said:
Ah, porting a rom from one model to the other is especially a ***** when they have a different baseband. I attempted it myself once, but I failed miserably...
Good luck with this btw, I hope you get somewhere with it
Keiran
Click to expand...
Click to collapse
Thank you , perhaps you can help me with this thought..
~In your [WIP][CDMA] MIUI for the R800x , on page 3, last post on the page, you said you were gonna try a port from the Evo 4g because "it is the only one with the same baseband (htc anyway)"~
Would I be wasting my time downloading / messing around with the baseband files for the Evo 4g to help me out with this project? Or does that not even make sense in my case? Im just trying to "try" everything and anything that may help
216Monster said:
Thank you , perhaps you can help me with this thought..
~In your [WIP][CDMA] MIUI for the R800x , on page 3, last post on the page, you said you were gonna try a port from the Evo 4g because "it is the only one with the same baseband (htc anyway)"~
Would I be wasting my time downloading / messing around with the baseband files for the Evo 4g to help me out with this project? Or does that not even make sense in my case? Im just trying to "try" everything and anything that may help
Click to expand...
Click to collapse
Different chipset, probably won't work
Sent from my R800x using Tapatalk
---------- Post added at 04:15 PM ---------- Previous post was at 03:58 PM ----------
Have you tried entering the have you tried entering the service menu (*#*#4636#*#*) and checked to make sure it was on CDMA (just an idea)
paxChristos said:
Different chipset, probably won't work
Sent from my R800x using Tapatalk
---------- Post added at 04:15 PM ---------- Previous post was at 03:58 PM ----------
Have you tried entering the have you tried entering the service menu (*#*#4636#*#*) and checked to make sure it was on CDMA (just an idea)
Click to expand...
Click to collapse
Yes I tried that already as well. It has "unknown" selected an will not allow me to select any of the other options. Thanks for inputing an idea though
Have you tried pulling the libril files from Verizon 2.3.3, and compared them to the ones on the gsm versions? (librils are located in /system/lib, and there are two of them)
Sent from my R800x using Tapatalk
paxChristos said:
Have you tried pulling the libril files from Verizon 2.3.3, and compared them to the ones on the gsm versions? (librils are located in /system/lib, and there are two of them)
Sent from my R800x using Tapatalk
Click to expand...
Click to collapse
I'm my op I posted a zip containing what I thought were all the 2.3.3 lib files for the baseband, are there more then what I have? I'm going to look again and see if I missed any.
Sent from my Droid using xda premium
216Monster said:
I'm my op I posted a zip containing what I thought were all the 2.3.3 lib files for the baseband, are there more then what I have? I'm going to look again and see if I missed any.
Sent from my Droid using xda premium
Click to expand...
Click to collapse
They might only work on your phone (I know I tried pushing some on a different phone from somebody else's and adb did not like) (I haven't checked your zip yet...)
Sent from my R800x using Tapatalk
paxChristos said:
They might only work on your phone (I know I tried pushing some on a different phone from somebody else's and adb did not like) (I haven't checked your zip yet...)
Sent from my R800x using Tapatalk
Click to expand...
Click to collapse
They should be all the same, but I tried the CM7 ril libs in the .62 rom and I still had service. I think it is more in terms of the phone.apk and stuff
Because the phone app seems to do more than it lets out, I think it also handles communications with the baseband and not just your dialer - but I could be wrong, I have as much knowledge as you do on this
Keiran
i don't know if it's phone.apk as much as /system/app/SemcTelephonyProvider.apk ...
KeiranFTW said:
They should be all the same, but I tried the CM7 ril libs in the .62 rom and I still had service. I think it is more in terms of the phone.apk and stuff
Because the phone app seems to do more than it lets out, I think it also handles communications with the baseband and not just your dialer - but I could be wrong, I have as much knowledge as you do on this
Keiran
Click to expand...
Click to collapse
I think the phone.apk is doing a lot aswell. Its taking some time but I'm going through every smali/xml file in the semcphone.apk looking for anything in regards to a baseband.
Sent from my Droid using xda premium
paxChristos said:
i don't know if it's phone.apk as much as /system/app/SemcTelephonyProvider.apk ...
Click to expand...
Click to collapse
The libs I posted in my zip are from a clean full ftf flash of verizon 2.3.3 firmware on my phone, they should work for all r800x since that's what they are from.
I'm gonna look into the telephonyprovider app it could be a piece of the puzzle I haven't discovered yet, I think the phone.apk is handling most of it because the cdma patch has only a semcphone.apk in it, but maybe the newer firmwares will need a patched phone apk and telephony apk.
Sent from my Droid using xda premium
Hey, I tried this with a little bit of testing, and i thought you might wanna look into this:
pulled the system and ran regrep (recursive grep, a linux script i have):
2.3.4 (62)
Code:
./etc/customization/content/com/sonyericsson/r2r/client/preloaded_config.xml:7780: <preloaded-data mnc="01" mcc="270" operator-name="L LUXGSM" service-provider="P&T Luxgsm" service-provider-id="215">
./etc/event-log-tags:124:50112 gsm_rat_switched (cid|1|5), (network_from|1|5), (network_to|1|5)
./etc/event-log-tags:125:50113 gsm_data_state_change (oldState|3), (newState|3)
./etc/event-log-tags:126:50114 gsm_service_state_change (oldState|1|5), (oldGprsState|1|5), (newState|1|5), (newGprsState|1|5)
./etc/permissions/handheld_core_hardware.xml:58: <!-- GSM phones must also include android.hardware.telephony.gsm.xml -->
./etc/permissions/android.hardware.telephony.gsm.xml:20: <feature name="android.hardware.telephony.gsm" />
regrep cdma (I made some changes)
Code:
./etc/customization/settings/cust.prop:8:ro.cdma.home.operator.alpha=Verizon
./etc/customization/settings/cust.prop:9:ro.cdma.home.operator.numeric=310004
./etc/customization/settings/cust.prop:10:ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
./etc/customization/settings/cust.prop:11:ro.cdma.otaspnumschema=SELC,1,80,99
./etc/event-log-tags:122:50110 cdma_data_setup_failed (cause|1|5), (cid|1|5), (network_type|1|5)
./etc/event-log-tags:123:50111 cdma_data_drop (cid|1|5), (network_type|1|5)
./etc/event-log-tags:127:50115 cdma_data_state_change (oldState|3), (newState|3)
./etc/event-log-tags:128:50116 cdma_service_state_change (oldState|1|5), (oldDataState|1|5), (newState|1|5), (newDataState|1|5)
./etc/permissions/handheld_core_hardware.xml:59: <!-- CDMA phones must also include android.hardware.telephony.cdma.xml -->
./build.prop:25:ro.cdma.home.operator.alpha=Verizon
./build.prop:26:ro.cdma.home.operator.numeric=310004
./build.prop:27:ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
./build.prop:28:ro.cdma.otaspnumschema=SELC,1,80,99
regrep cdma (2.3.3)
Code:
./etc/customization/settings/cust.prop:12:ro.cdma.home.operator.alpha=Verizon
./etc/customization/settings/cust.prop:13:ro.cdma.home.operator.numeric=310004
./etc/customization/settings/cust.prop:14:ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
./etc/customization/settings/cust.prop:15:ro.cdma.otaspnumschema=SELC,1,80,99
./etc/event-log-tags:120:50110 cdma_data_setup_failed (cause|1|5), (cid|1|5), (network_type|1|5)
./etc/event-log-tags:121:50111 cdma_data_drop (cid|1|5), (network_type|1|5)
./etc/event-log-tags:125:50115 cdma_data_state_change (oldState|3), (newState|3)
./etc/event-log-tags:126:50116 cdma_service_state_change (oldState|1|5), (oldDataState|1|5), (newState|1|5), (newDataState|1|5)
./etc/permissions/handheld_core_hardware.xml:59: <!-- CDMA phones must also include android.hardware.telephony.cdma.xml -->
./etc/permissions/android.hardware.telephony.cdma.xml:20: <feature name="android.hardware.telephony.cdma" />
./build.prop:28:ro.cdma.home.operator.alpha=Verizon
./build.prop:29:ro.cdma.home.operator.numeric=310004
./build.prop:30:ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
./build.prop:31:ro.cdma.otaspnumschema=SELC,1,80,99
Update:
I know that Verizon downloads the data for APN to your phone for you (stupid Verizon)
When I tried putting in the APN, and clicked save, it didn't save... any ideas?
Just another Idea, does anybody know where it checks for the sim card?
---------- Post added at 08:42 AM ---------- Previous post was at 08:38 AM ----------
Interesting link (stackoverflow is perhaps the awesomest website ever, gave me a link to here)
Telephony manager does do alot of more than just sit there, we might wanna look into that and see what's pointing to it...
link: http://developer.android.com/reference/android/telephony/TelephonyManager.html
paxChristos said:
Just another Idea, does anybody know where it checks for the sim card?
Click to expand...
Click to collapse
I think the baseband does that
Sent from my R800i using Tapatalk
Sorry for writing here but I am not authorized to write in the same post. I hope I could be able in near future
I need to know how to root the new MIUI 2.8.3 ?
Thanks for every one worked on it
Regards
sherifaly said:
Sorry for writing here but I am not authorized to write in the same post. I hope I could be able in near future
I need to know how to root the new MIUI 2.8.3 ?
Thanks for every one worked on it
Regards
Click to expand...
Click to collapse
is there any application that called superuser or supersu ?
On the home screen you will see tools folder, open it then find permission (the icon like paper script) open that then choose manage root permission
Sent from my PC36100 using Tapatalk 2
nom051205 said:
On the home screen you will see tools folder, open it then find permission (the icon like paper script) open that then choose manage root permission
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I did that but it doesnt work , Also I flashed the superuser in this thread http://forum.xda-developers.com/showthread.php?t=997581
It always says superuser deny the apps.
Also regaridng battery I see you mention that it stays for only 5 hours , it stays with me for 20 hours with regular conditions & I am using battery deffender.
If I have any other comments I will mention it but we must root it
Again thanks for the good job
This rom is already pre-rooted no need to flash any thing as we generally do in stock roms.......
I think you have flashed some superuser.....so i think you need to re- flash the rom-(***do make a clean rom flash asper rom developer***)
Now after rom instal just instal root explorer......
Now as soon as u open root explorer a menu popup will apear it is just like superuser pop up ...(only the diffrence is this pop up will apear for 20sec...and contains so many warning message all u need to click next every time) (****refer attached images ****)
After this step you can see root folder .....
For every application which asks for root permission. U need to do this .....
Adi.
sherifaly said:
I did that but it doesnt work , Also I flashed the superuser in this thread http://forum.xda-developers.com/showthread.php?t=997581
It always says superuser deny the apps.
Also regaridng battery I see you mention that it stays for only 5 hours , it stays with me for 20 hours with regular conditions & I am using battery deffender.
If I have any other comments I will mention it but we must root it
Again thanks for the good job
Click to expand...
Click to collapse
Now that weird, I have no issue with su on mine, maybe you should reflash the rom?
Sent from my PC36100 using Tapatalk 2
nom051205 said:
Now that weird, I have no issue with su on mine, maybe you should reflash the rom?
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I followed what jyeshta001 mentioned and it goes fine with me.
The point now that the screen turnes with some colors ( you can enter VPN and you will see it ). also it is very laggy and it make many restarts. aslo headset problem still exists,the automatic brightness & buttons lighting during press on it.
I have a question abour RAM as most of time it works with 100MB free only ( can we make any thing with that )
Finally Thanks to jyeshta001 for his replay.
Thanks to nom051205 for the rom and we hope to see further development
I have some time to support but I dont have any experince in roms editing so if you can advice with some links I could support.
Best regards
sherifaly said:
I followed what jyeshta001 mentioned and it goes fine with me.
The point now that the screen turnes with some colors ( you can enter VPN and you will see it ). also it is very laggy and it make many restarts. aslo headset problem still exists,the automatic brightness & buttons lighting during press on it.
I have a question abour RAM as most of time it works with 100MB free only ( can we make any thing with that )
(QUOTE=sherifaly;32178538)
Use rom tool box pro / a strong startup manager so that u can control unwanted application running form the begining for startup.....
For head set one use a wedget called "toggle to head set" from playstore.
For lagness use any CPU tool like set CPU and set frequency as "1xx to 1xxx " and the governor to "on demand" (but drains battery)
For button lights "root dim " aPK. Will help u to some extend ......
For random colours on screen we will have to w8 "Nom bro" will bring a patch ....soon .....
Adi!™
Click to expand...
Click to collapse
jyeshta001 said:
sherifaly said:
I followed what jyeshta001 mentioned and it goes fine with me.
The point now that the screen turnes with some colors ( you can enter VPN and you will see it ). also it is very laggy and it make many restarts. aslo headset problem still exists,the automatic brightness & buttons lighting during press on it.
I have a question abour RAM as most of time it works with 100MB free only ( can we make any thing with that )
(QUOTE=sherifaly;32178538)
Use rom tool box pro / a strong startup manager so that u can control unwanted application running form the begining for startup.....
For head set one use a wedget called "toggle to head set" from playstore.
For lagness use any CPU tool like set CPU and set frequency as "1xx to 1xxx " and the governor to "on demand" (but drains battery)
For button lights "root dim " aPK. Will help u to some extend ......
For random colours on screen we will have to w8 "Nom bro" will bring a patch ....soon .....
Adi!™
Click to expand...
Click to collapse
Thanks my friend I will try all
But now the market is mentioning the device is not compatible with this app , what shall I do ??? knowing that I changed the resoluation to 180 DPI.
Thanks in advance
Click to expand...
Click to collapse
sherifaly said:
jyeshta001 said:
Thanks my friend I will try all
But now the market is mentioning the device is not compatible with this app , what shall I do ??? knowing that I changed the resoluation to 180 DPI.
Thanks in advance
Click to expand...
Click to collapse
Open the build.prop(this file is in system folder) in text editor of root explorer and add following lines at the end of build prop page ...
ro.product.model=GT-N7000
ro.product.manufacturer=samsung
Then save &exit ....after that you should do a reboot.
Now check ur market compatability .... if this is not working then change the model number and manufacture name to some other one..... on above lines....
Give us the feedback if it is not working.....ok
Adi™
Click to expand...
Click to collapse
jyeshta001 said:
sherifaly said:
Open the build.prop(this file is in system folder) in text editor of root explorer and add following lines at the end of build prop page ...
ro.product.model=GT-N7000
ro.product.manufacturer=samsung
Then save &exit ....after that you should do a reboot.
Now check ur market compatability .... if this is not working then change the model number and manufacture name to some other one..... on above lines....
Give us the feedback if it is not working.....ok
Adi™
Click to expand...
Click to collapse
Thanks again my friend it works fine.
I will check the mentioned progarms & give my feed back.
Best regards
Click to expand...
Click to collapse
sherifaly said:
jyeshta001 said:
Thanks again my friend it works fine.
I will check the mentioned progarms & give my feed back.
Best regards
Click to expand...
Click to collapse
Regarding market also LCD density modder pro willl solve the problem
New problem appears , Viber & Tango are not working after searching I found some body mentioned a problems with mic ( in custom roms)
Any ideaes about that
Click to expand...
Click to collapse
sherifaly said:
sherifaly said:
Regarding market also LCD density modder pro willl solve the problem
New problem appears , Viber & Tango are not working after searching I found some body mentioned a problems with mic ( in custom roms)
Any ideaes about that
Click to expand...
Click to collapse
yes viber, tango, skype not working only on those custom roms which are based on 2.3.7 and also all ics roms
Click to expand...
Click to collapse
citric_acid said:
sherifaly said:
yes viber, tango, skype not working only on those custom roms which are based on 2.3.7 and also all ics roms
Click to expand...
Click to collapse
who says skype not working? you better search carefully... there are workaround for 2.3.7 already...
Click to expand...
Click to collapse
deysmacro said:
citric_acid said:
who says skype not working? you better search carefully... there are workaround for 2.3.7 already...
Click to expand...
Click to collapse
okay, so did you try that trick, i think after trying you shouldn't have said that, even though what about those who does'nt want to credit there accounts, also ive mentioned about 4.0.4 roms, i know that they won't work on them since they're still on development stage so its better to stay on 2.3.3 for frequent voiper's
Click to expand...
Click to collapse
citric_acid said:
deysmacro said:
okay, so did you try that trick, i think after trying you shouldn't have said that, even though what about those who does'nt want to credit there accounts, also ive mentioned about 4.0.4 roms, i know that they won't work on them since they're still on development stage so its better to stay on 2.3.3 for frequent voiper's
Click to expand...
Click to collapse
Yes also viber is orking in 2.3.7 I tries it in Longhorn & others
Click to expand...
Click to collapse
I try to ask another question as if my past four questions never answered by noone...anyway i will try...its free after all!
I wanna port a rom from a device similar to mine...cos mine device has zero (0) developers there are plenty devices with my board...like desire HD, SE Neo V, Desire S, Xperia T...and so on....my device have the msm7630 board...but for some strange reason the few chinese devs and the official rom made by Huawei i forgot my device is the Ideos X5 pro with msm7630 board, the chinese devs and the official GB,ICS rom are using the same as the past version of the mobile the Ideos X5 (non pro) the msm7x30_surf...they have it on build.prop also the .so files on system/lib/hw are called _surf.so files...so there are plenty of roms that we can use but they using the msm7630 board if i simply do as we do with other huawei phones simply change the build.prop and use our own kernel (3.0.8) the phone boots but if we use our kernel but desire HD rom...the phone stuck on bootscreen...so there are files releated to the board on the kernel??i think yes but im not sure..and how can we port a rom like this...remember the boards are the same everywhere i look we use the msm7630 board not the msm7x30_surf board...
So if someone could pls help me and answer this thread i will be greatful!! thanks!
Also if there is a Greek developer with will to help me pls pm me!
ok use your phones boot.img(kernel+ramdisk)
this way adb will load up
then check for errors in libs like error xyz.so couldnt load up then do a adb push or get into the system somehow get a logcat....
or
if u think most of the hardware is the same
use that config as base and make mods to suit ur device then compile any rom from source...
speed_bot said:
ok use your phones boot.img(kernel+ramdisk)
this way adb will load up
then check for errors in libs like error xyz.so couldnt load up then do a adb push or get into the system somehow get a logcat....
or
if u think most of the hardware is the same
use that config as base and make mods to suit ur device then compile any rom from source...
Click to expand...
Click to collapse
Im thrilled soneone answer me thanks!
I try it but it stuck on splash logo and cant use logcat at all only getting an error on memmove related to system/bin/sh file!
I can understand they way of compiling even with no major programming knowlage but cant find a proper allinone source!they have device vendor programs framework kernel which one of them is the proper source!
Sent from my U8800Pro using xda premium
pikachukaki said:
Im thrilled soneone answer me thanks!
I try it but it stuck on splash logo and cant use logcat at all only getting an error on memmove related to system/bin/sh file!
I can understand they way of compiling even with no major programming knowlage but cant find a proper allinone source!they have device vendor programs framework kernel which one of them is the proper source!
Sent from my U8800Pro using xda premium
Click to expand...
Click to collapse
your error might be this
error
system/bin/sh no file or directory am i right in this regard ...??
---------- Post added at 10:41 PM ---------- Previous post was at 10:39 PM ----------
pikachukaki said:
Im thrilled soneone answer me thanks!
I try it but it stuck on splash logo and cant use logcat at all only getting an error on memmove related to system/bin/sh file!
I can understand they way of compiling even with no major programming knowlage but cant find a proper allinone source!they have device vendor programs framework kernel which one of them is the proper source!
Sent from my U8800Pro using xda premium
Click to expand...
Click to collapse
if you want i can explain you with some basic stuff ...
if u like then i will proceed
speed_bot said:
your error might be this
error
system/bin/sh no file or directory am i right in this regard ...??
---------- Post added at 10:41 PM ---------- Previous post was at 10:39 PM ----------
if you want i can explain you with some basic stuff ...
if u like then i will proceed
Click to expand...
Click to collapse
My error was this
logcat
soinfo_relocatelinker.cpp:975: cannot locate symbol "__memmove_chk" referenced by "/system/bin/sh"...CANNOT LINK EXECUTABLE
I was using android commander to get to logcat no luck then i search here on xda for some GUI logcats i found a qtadb something like that and it gave me this only...no more and the phone stuck at splash screen...
I love to learn more cos as i said we dont have any dev and i like for myself to learn more...if you want you can or i can pm you my gtalk,msn whatever you want so we dont spam here!!
pikachukaki said:
My error was this
logcat
soinfo_relocatelinker.cpp:975: cannot locate symbol "__memmove_chk" referenced by "/system/bin/sh"...CANNOT LINK EXECUTABLE
I was using android commander to get to logcat no luck then i search here on xda for some GUI logcats i found a qtadb something like that and it gave me this only...no more and the phone stuck at splash screen...
I love to learn more cos as i said we dont have any dev and i like for myself to learn more...if you want you can or i can pm you my gtalk,msn whatever you want so we dont spam here!!
Click to expand...
Click to collapse
pm me your skype id
speed_bot said:
pm me your skype id
Click to expand...
Click to collapse
Ok i pm you...im happy you wanna help!!
yes i have seen the post all over the forum, but i didn't figure how to fix the problem. i have a stupid MT6628 mobile phone with android 4.0.4 with kernel version 3.0.13.
i have read somewhere about changing something in the packages.xml file so i attached mine in case anyone would be kind enough to tell me what exactly i have to delete/add/edit/whatever
thank you
oh and yes it is a rooted device
RockyAJ said:
yes i have seen the post all over the forum, but i didn't figure how to fix the problem. i have a stupid MT6628 mobile phone with android 4.0.4 with kernel version 3.0.13.
i have read somewhere about changing something in the packages.xml file so i attached mine in case anyone would be kind enough to tell me what exactly i have to delete/add/edit/whatever
thank you
oh and yes it is a rooted device
Click to expand...
Click to collapse
are you on custom rom?
usually custom roms show that notification
sangalaxy said:
are you on custom rom?
usually custom roms show that notification
Click to expand...
Click to collapse
it is a chinese mobile phone.and i saw a workaround for it,but didn't know how to fix it myself, hence i attached my packages.xml for someone to be generous enough to just tell me what changes i have to make to the file
RockyAJ said:
it is a chinese mobile phone.and i saw a workaround for it,but didn't know how to fix it myself, hence i attached my packages.xml for someone to be generous enough to just tell me what changes i have to make to the file
Click to expand...
Click to collapse
sorry friend Idk to edit the package too
if you are rooted you can try flashing the latest gapps package that should fix this and try fixing permissions
if you are not rooted then wait for someone to edit it for you or do a search and do it yourself
sangalaxy said:
sorry friend Idk to edit the package too
if you are rooted you can try flashing the latest gapps package that should fix this and try fixing permissions
if you are not rooted then wait for someone to edit it for you or do a search and do it yourself
Click to expand...
Click to collapse
i am rooted and i tried flash the gapps but it gave an error.something like wrong package or something...
so no one is kind enough to just do this which would take a practiced one, less than a minute? how sweet
I'v been using this for long time now... so i decided to make a flashable zip of it and share with you guys
Features included
1. native call recording.. (check screenshot)
2.enable/disable camera shutter sound,
3.IP calling option, (still don't know whats the use of it ,
4. etc...
Downoads
http://www.mediafire.com/?8wu5y5pcdufq3mm
cool
cool @gody420 will be of great use I will test !
Error :'(
is giving the following error failed to save.
Sorry my english
Thanks @gody420
robertcarvalho20 said:
is giving the following error failed to save.
Sorry my english
Thanks @gody420
Click to expand...
Click to collapse
its working without any problem for me.. try to delete system/csc folder den flash the zip...
Error continued
Failed man, performed the procedure but did not work .
Thanks @gody420 !
robertcarvalho20 said:
Failed man, performed the procedure but did not work .
Thanks @gody420 !
Click to expand...
Click to collapse
which rom r u using and whats ur problm.. r u not able to save recorded audio?
I'm in development!
gody420 said:
which rom r u using and whats ur problm.. r u not able to save recorded audio?
Click to expand...
Click to collapse
Deodex the bubuanh1 and am working the error and save the audio not saved!
need help desperately
I flashed it I got all the features but after that when ever I receive a call it shows only contact number not the name.
Please kindly suggest me a solution or a way to revert back to normal pleaseeeeee......
:crying:
Problem Solved
I did some net search and found a way to revert back to normal.
all we need to do is to delete the CSC folder in system files
miky144 said:
I did some net search and found a way to revert back to normal.
all we need to do is to delete the CSC folder in system files
Click to expand...
Click to collapse
thnx bro :good::good::good::good::good::good::good: