[Q] Xperia Arc | CM9.0 | FXP106| Can't add any APN's - Xperia Arc Q&A, Help & Troubleshooting

Hello,
I flashed my Arc with baseband 62 on the latest CM 9.0 FXP106. I'm pretty satisfied so far. The only thing that bugs me is that it seems that I can't add any APN's. That means if I want to add a new APN and I want to save it, it won't let me do it.
I tried backing it up with APNsBU (ROOT) -> didn't work
Hard reset -> didn't work
Fixing permissions in ROM Manager -> didn't work
Thanks for your help!

1.) Have you heard of posting in the relevant thread?
2.) It's a known bug. Read before post and use the search!
Sent from my LT18i using xda premium

Hey,
as I don't have 10 posts yet I can't post in the CM9.0/FreeXperia Thread.
I actually looked through a lot of posts and didn't find any relevant help.
Thanks for your reply though.

dont find it?it is already mention posted so many time..
Sent from my LT18i

this problem is in all xperia 2011, few networks operate

I have the same problem, does anyone know a way around this?

monstercable said:
I have the same problem, does anyone know a way around this?
Click to expand...
Click to collapse
Bin4ary posted a probably way to fix it, check out CM9's thread for more information.
Bin4ry said:
From what i can tell now the problem is that in CM9 we are using the ICS (ofc ) RIL-structure. There are already some oldRil features implemented, but this features are mainly for phones which use standard communications. We are having this weird Qualcomm RIL which acts different. For example we have no Status which tells System that SIM is ready, this status is piggybacked for us in another call.
On the other side we SE implemented some more messages for additional informations. For example: OperatorInfo is not standard one, it has one more entry.
So i need to go through the lines and check we're i can implement the different structure well without breaking other devices. Maybe i am able to trigger all needed parcel reads from RIL, maybe not. The main difference is lying in some other files which was still working in GB RIL structure.
Please wait for next week when i am able to work again on this issue. It's annoying me too
No. I will work on GSM data. Jerpelea will fix this problem ASAP.
Since we are 2 people working on this CM9 for the SE phones we can split the work.
And it is always better to work on 1 problem after another.
You see, 2 people -> 2 Todo lists
Regards
Click to expand...
Click to collapse

Thanks for your help. I didn't get that this was related to the APN issue.

Related

[DEV] ION 1.6 (Donut)

Disclaimer: For devs only. Updating to it will wipe your device. I am not responsible of any damage of any sort or data loss or anything.
Google Ion 1.6 for HTC Hero.
This project aims at getting the stock Google Ion Rom to run on HTC Hero. No Rosie or any HTC apps will be ever added to that rom. Once fully functional it could be used as a base for cookers.
Current release: Lox-ION-1.0b3 (logcat)
What works:
- place, receive calls
- wifi
- Market
- GPRS
What does not do far
- bluetooth (logcat seems it is relative to libc.so - Uncompatible with current kernel ?)
- trackball
- compass & accelerometer (with akmd > logcat - with ak8973 > logcat )
- GPS
- camera
Note: devs please test hack and share if you fix anything or have any idea
Great! I hope the rest will be fixed soon!
I second that!
Great to hear it.
are you working on the hardware that doesn't work? and whats the progress.
you forgot to mention that the camera doesnt work aswell
Just flashed it, gonna see what I can get working(if anything).
I'd like to try it - but can you go back by using Nandroid - or reflashing Modaco's ROM ( I'm on 2.3 )
J-Zeus said:
I'd like to try it - but can you go back by using Nandroid - or reflashing Modaco's ROM ( I'm on 2.3 )
Click to expand...
Click to collapse
yes you can
I dont know how gecka feels but could we try and keep this thread informative
Just did a bit of snooping around and the GPS does work, you sure you checked it right? I did a bit of tinkering but none of it was related to the GPS at all. Trackball I'm still not sure about, the keylayouts have the same keycodes but still doesn't seem to want to work. Accelerometer just needs the permission to be granted to execute, except I'm not to sure how to do that cause I'm a bit new to linux. As for the bluetooth, don't get me started, its giving me a headache lol xD
hey i m using this rom and its working beautiful...man nice job and the trackball blinks when a phone is ringing ....but doesnt blind at the time of reminders....but still great job...
What about headphone detection? I know with the other Ion ROMs, when you plugged in headphones, it went unnoticed unless you downloaded an app to manually switch the audio over.
For devs only!
Hi guys,
Please, consider the [DEV] in the subject: this thread is for devs only.
If you don't give any fix, just follow the thread by subscribing to it and don't polute it! Thanks.
For now this build is buggy, you'll certainly find more and more bugs, witch I don't care for now as I want main functionality to work first (bluetooth, gps etc...)
robertosandros said:
Just did a bit of snooping around and the GPS does work, you sure you checked it right?
Click to expand...
Click to collapse
Please read carrefully before posting. GPS in in the "not working" list....
robertosandros said:
Accelerometer just needs the permission to be granted to execute
Click to expand...
Click to collapse
Right! Wrong permissions on witch file ???
Good work gecka,
I'm downloading to have a lookie and install now, see if I can have a go at the trackball.
Can I ask a question though, whats actually involved in fixing these issues?? Is it blind luck playing with config settings and that, or are you getting debug output?
kwiksand said:
Can I ask a question though, whats actually involved in fixing these issues?? Is it blind luck playing with config settings and that, or are you getting debug output?
Click to expand...
Click to collapse
Well, both in fact. The only debug output I get is from logcat and device logs.
Some issues might also be tight to kernel version.
But please there is a how to cook thread
gecka said:
Please read carrefully before posting. GPS in in the "not working" list....
Right! Wrong permissions on witch file ???
Click to expand...
Click to collapse
Thats what I'm saying, you've listed GPS as not working but its working for me.
Still trying to figure that part out
robertosandros said:
Thats what I'm saying, you've listed GPS as not working but its working for me.
Still trying to figure that part out
Click to expand...
Click to collapse
You sure the phone is not locating you based just on nearby cell towers?
gecka said:
Well, both in fact. The only debug output I get is from logcat and device logs.
Some issues might also be tight to kernel version.
But please there is a how to cook thread
Click to expand...
Click to collapse
i dount known if this works but maybe, behnaam haw gotten Accelerometer (Screen rotation) Fixed!
http://forum.xda-developers.com/showthread.php?t=563772
haw u triad hes files? maybe works and maybe u using different kernel ver
Market Apps
Hey all.
We've got a problem with the Donut Market over in the Vogue forums. In Donut, when we load up the Market, there are only 20-30 apps available. Going back to Cupcake builds, the problem persists. However, logging in with a fresh Gmail account gets rid of the problem (in Cupcake.)
So far, my guess as to the cause of this is that Google's server have taken note of any "pirates" accessing the as-of-yet unreleased Donut market, and locked them out. However, I don't see any complaints along those lines here.
So, my question to all of you is, while you say the Donut Market is working, do you still seem to have access to all the applications you did in Cupcake?
craig0r said:
Hey all.
We've got a problem with the Donut Market over in the Vogue forums. In Donut, when we load up the Market, there are only 20-30 apps available. Going back to Cupcake builds, the problem persists. However, logging in with a fresh Gmail account gets rid of the problem (in Cupcake.)
So far, my guess as to the cause of this is that Google's server have taken note of any "pirates" accessing the as-of-yet unreleased Donut market, and locked them out. However, I don't see any complaints along those lines here.
So, my question to all of you is, while you say the Donut Market is working, do you still seem to have access to all the applications you did in Cupcake?
Click to expand...
Click to collapse
whats your build.prop?

[Q] Some WIFI Problems with FROYO X on Rhod210 - HTC Touch Pro 2

Hi, I noob on this of an Android Phone, I have a HTC TOUCH PRO 2, RHOD210.
I install the FROYO X 2011.01.12 and i put the kernel that have the packet than run the camera and this is OK.
My problem is that the wifi interface is not workink, i am try a lot of solutions that found in this forum, but nothing is ok for me, i change the rootfs like suggest in a forum, modify the wifi-nvram.txt and put the mac address of the wifi, i update the kernel to Latest Kernel Commit# 1253, and i have the same problem.
could someone tell me how to solve the wifi of my rhod210?
Please, I do not want to use windows mobile
How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...
arrrghhh said:
How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...
Click to expand...
Click to collapse
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....
kleper said:
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....
Click to expand...
Click to collapse
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?
arrrghhh said:
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?
Click to expand...
Click to collapse
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.
kleper said:
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.
Click to expand...
Click to collapse
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Also, I'm not sure what you mean "slow with this kernel" - by vanilla FRX03 build, I mean the complete bundle - not just the kernel. Plus, kernels are not tied to system images... So I'm not sure what you mean.
arrrghhh said:
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Click to expand...
Click to collapse
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.
kleper said:
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.
Click to expand...
Click to collapse
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.
arrrghhh said:
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.
Click to expand...
Click to collapse
I do that, and don't work for me.
Thanks
kleper said:
I do that, and don't work for me.
Click to expand...
Click to collapse
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.
arrrghhh said:
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.
Click to expand...
Click to collapse
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?
how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?
kleper said:
how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?
Click to expand...
Click to collapse
Sticker underneath the battery - not on the battery itself. It's usually in tiny gray font.
kleper said:
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?
Click to expand...
Click to collapse
Well, I'd format with the HP tool. (Full format, FAT32) Download this bundle as well.
[SOLVED]
Thank you very much to everyone who answered me and all the developers of this project so interesting, yesterday succeeded in solving the problems I had, my SD formatting, reinstalling Froyo x version 2011.01.12 and puts a kernel of the chamber, after That did the trick again wifi-nvram.txt file, according to the link that let me arrrghhh one of the threads of this forum, after that the WIFI has started to work wonders.
Then my HTC Touch Pro 2, RHOD210 remain with:
WIFI
CAMERA
GPS
PHONE, DATA AND YOU
AUDIO
Thank you very much.
Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !
eu0741924381 said:
Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !
Click to expand...
Click to collapse
WEP actually seems to work on mine. Strange as that is.
Other problems
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?
kleper said:
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?
Click to expand...
Click to collapse
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
jchutch2 said:
WEP actually seems to work on mine. Strange as that is.
Click to expand...
Click to collapse
WEP should never, ever be used in any circumstances if it can be avoided. That protocol is extremely insecure...
arrrghhh said:
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
Click to expand...
Click to collapse
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much
kleper said:
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much
Click to expand...
Click to collapse
Well, I'd recommend 1250 then I guess... Usually I recommend the newest GIT kernel, which is currently 1253.
FYI, you already can remove Windows and flash the device to run Android natively. It's just not as stable as haret, but it's getting there. Plus, it's only a partial NAND boot - only init and the zImage are actually loaded on the MTD if I'm not mistaken, everything else is on the SD card (which is still 99% of the data...)
But, if you're feeling brave and really do want to completely get rid of WinMo, NAND boot away... can't say I didn't warn ya

2.3.4 MMS Question for AOSP Roms

No rush but was curious if any developer's were getting close to fix with the pic download mms for the 2.3.4 roms ?
Its getting close with nightly 72...hopefully in the next nightly.
mrjaydee82 said:
No rush but was curious if any developer's were getting close to fix with the pic download mms for the 2.3.4 roms ?
Click to expand...
Click to collapse
asking for ETA's is a major no no ... but i agree im waiting on a fix myself
mrjaydee82 said:
No rush but was curious if any developer's were getting close to fix with the pic download mms for the 2.3.4 roms ?
Click to expand...
Click to collapse
simple answer is that you'll see a bunch of posts when it's fixed, it's being actively worked on but it's not a simple fix
In very much layman's terms, can anyone explain how something like this gets broken? Why does it work in one version and then not in the next? Thanks!
Different phones use different settings and different servers. Different networks use totally different ways of handling messages.
thanamesjames said:
In very much layman's terms, can anyone explain how something like this gets broken? Why does it work in one version and then not in the next? Thanks!
Click to expand...
Click to collapse
dabbill said:
Different phones use different settings and different servers. Different networks use totally different ways of handling messages.
Click to expand...
Click to collapse
that, and that code gets re-written, updated, etc.
something gets updated or fixed, and some other thing could break because of it... what I do know is that CM is a community project, with amazing devs, and they are dealing with cutting edge software. we gotta remember that 2.3.4 is only (officially) on two phones right now, the Nexus One and Nexus S, both Google phones.
Someone posted a fix on the nightlies thread: MMS Fix Here

[Q] cyanogenmod ROM (cdma) issue

It seems those working on this ROM don't like to keep people updated so I must fix this myself, but I need help. I'm on the latest cyanogen ROM and mms does not work. It will not send whether on wifi or regular. Does ANYONE have any suggestions of where to look to fix this. I'm not a newb by any means, I've just never ran into anything like this. So any help would be appreciated.
On a side note, not all new members on XDA have no clue so I find it rude and discriminatory to label them as such by not letting them post on the development page and other annoying issues.
agraceful said:
It seems those working on this ROM don't like to keep people updated so I must fix this myself, but I need help. I'm on the latest cyanogen ROM and mms does not work. It will not send whether on wifi or regular. Does ANYONE have any suggestions of where to look to fix this. I'm not a newb by any means, I've just never ran into anything like this. So any help would be appreciated.
On a side note, not all new members on XDA have no clue so I find it rude and discriminatory to label them as such by not letting them post on the development page and other annoying issues.
Click to expand...
Click to collapse
This has been a well known issue with the CDMA ROM for several months now. Its by no means knew news. If you would have read the thread for more than 2 pages, you would have seen that. I'm working on a fix for the MMS issue, so we can have a flawless ROM.
Sent from my R800x
Leraeniesh said:
This has been a well known issue with the CDMA ROM for several months now. Its by no means knew news. If you would have read the thread for more than 2 pages, you would have seen that. I'm working on a fix for the MMS issue, so we can have a flawless ROM.
Sent from my R800x
Click to expand...
Click to collapse
I actually read about 50 pages worth and saw nothing. But atleast someone is working on it. I'm going to rip apart the stock ROM and see what I can find. I'm use to working on motorolas, but again, thank you.

rooting 'Infotmic sawee10'

i am having trouble finding a thread on how to root and rom flash the "infotmic sawee10" if someone could help me out with a link or smething it would be much appreciated!!!!
gearhead3585 said:
i am having trouble finding a thread on how to root and rom flash the "infotmic sawee10" if someone could help me out with a link or smething it would be much appreciated!!!!
Click to expand...
Click to collapse
flytouch 2 or 3? w/ android 2.2 right?
Solidus_n313 said:
flytouch 2 or 3? w/ android 2.2 right?
Click to expand...
Click to collapse
shizznit! its for a friend.... its on 2.2 i kno that....
what other specs are needed?
she said its an "infotmic sawee10"..... from websurfing i found out its a clone of flytouch but that about it..... ppl @slatedroid are no help, all they do is delete my post...
i dont own one personally, but ive used a friends once or twice, and he asked me the same thing its relly difficult to pinpoint the model, but these are usually the differneces:
1. what color is the power light / Charge
2. does it vibrate on start up
3. any model info
4. WMT version, Can be found in setting about(if its a WonderMedia Technologies)
5. Download and use Android system info look at the memory (There are some vendors that fake the mem.)
6. look at the build.prop for any vendor info
EDIT** these instructions should help you root:
http://thebelv.altervista.org/Flytouch3/rooting/rooting_flytouch3.html
cool brah! thnx! ill get the spec asap! really appreciate the help!! ppl @ slatedroid were making me RAGE!! lolz
also, do you know the specs for screen resolution (1024x600 or 1024x576) and charger (9v or 5v)?
ok regardless of HW info, im 99% certain you have a KIRF, so your options are limited (read* non-existant ) for ROMS...
root wont be a problem, there are several methods. but the big issue is flashing roms over USB+mem stick(only gaurenteed method) has been known to cause more bricks than quality results with the SAWEE10/MERCURY...
i recommend ROOT + Titanium Backup (clear bloat) + System Panel/task killer (eliminate unnecessary processes) + New Launcher (your choice [or hers, whichever], its ALWAYS user preference ;P) to optimize the tablet.
ill PM you a bunch of links to help with these efforts and shed some light on this mess of a shadow tablet
Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.
IAmTheOneTheyCallNeo said:
Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.
Click to expand...
Click to collapse
wow, i miss people like you here on XDA
Solidus_n313 said:
wow, i miss people like you here on XDA
Click to expand...
Click to collapse
Thanks Yeah this place has become a demanding :handouts now: type of place lately with people who will chastise you should you accidentally ask a question that was previously answered in some hidden grave deep within the thread lol. However there are still a lot of good people here. I support the Droid Incredible on xda along with all my mods and tweaks that are across platform, and then my tablet on slatedroid. I don't know what was happening to this new user's posts but it really set him off. I'm glad you were able to provide him some info. If you feel like exploring a new community bent on being "chastise free", look up AndroidPassions.com. ****Mods and Admins my post is in no way intended to pull members away from this site but rather offer another avenue for additional support of their device: ) ****
Sent from my ADR6300 using Tapatalk
hahaha nice cover
ive been with xda for a LONG time, and delt with A LOT of trolls and useless blockheads who would rather you fix the problem than learn to fix it themselves with the help of others, hence the current state of XDA...people with more money than brains who think they deserve your hands on help becuase they figured out how to register to the forum
so i dont think ill ever actually leave permanantly, but ill say this, this isnt my first account :/
IAmTheOneTheyCallNeo said:
Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.
Click to expand...
Click to collapse
thanks neo!!! idk what happened over there... all i kno is that my post werent showing.... n i was getting heated.lol.
ill be keeping THIS thread up-to-date with all steps n issues if any!! appreciate the help!
Solidus_n313 said:
i dont own one personally, but ive used a friends once or twice, and he asked me the same thing its relly difficult to pinpoint the model, but these are usually the differneces:
1. what color is the power light / Charge
2. does it vibrate on start up
3. any model info
4. WMT version, Can be found in setting about(if its a WonderMedia Technologies)
5. Download and use Android system info look at the memory (There are some vendors that fake the mem.)
6. look at the build.prop for any vendor info
EDIT** these instructions should help you root:
http://thebelv.altervista.org/Flytouch3/rooting/rooting_flytouch3.html
Click to expand...
Click to collapse
look at build.prop for vendor? where do i find this? about tablet?
spec info:
infotmic sawee10
power / charge light - red
vibrates on start-up - yes
loading screen number - 0.6.1.2(672)
settings->about device:
model number- sawee10
android version - 2.2 v2.1:#3925
baseband version - unknown
kernel version - 2.6.32.9 [email protected] #82
build number - frf858
got the link to "rooting flytouch3" thanks!!
android system info installed from market.
let me kno what else is needed!! thanks!
gearhead3585 said:
spec info:
infotmic sawee10
power / charge light - red
vibrates on start-up - yes
loading screen number - 0.6.1.2(672)
settings->about device:
model number- sawee10
android version - 2.2 v2.1:#3925
baseband version - unknown
kernel version - 2.6.32.9 [email protected] #82
build number - frf858
got the link to "rooting flytouch3" thanks!!
android system info installed from market.
let me kno what else is needed!! thanks!
Click to expand...
Click to collapse
Yours vibtates? Hrrmmmmm.... that's interesting.. Hey my rooting method on slate is probably the simplest. I also included z4root as a direct download. Should be in post #2. Rooting with z4method can't screw it up
Sent from my ADR6300 using Tapatalk
Ok sounds great! And what about the rom flash to 2.3?? That's all good too then also??
Sent from my HTC Glacier using XDA App
gearhead3585 said:
Ok sounds great! And what about the rom flash to 2.3?? That's all good too then also??
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
It's not a real 2.3.. it's a 2.2 mutant lol it lies. I discourage your flashing of the roms mainly because yours came sawee and not tab10. Although the rom most likely will work, you run the risk or losing wifi.. even mine having been tab 10 even providing the correct drivers/firmware was unable to get the internal wifi functional again. So I purchased a $13 nano USB dongle and it works fantastic. Should you decide to take the risk, I would try the official ibex build on my page or the sawee build.
Sent from my ADR6300 using Tapatalk
ok cool. ill just do a theme upgrade with adw or something then, really appreciate the help guyz!!

Categories

Resources