Well, since our old thread was locked, and since I'm continuing the development, the new thread is here. Many thanks to ajeet17181 for giving me the final piece of the puzzle to resume the work.
I am continuing ajeet17181's work on bringing a working Android build to our Windows Mobile phone, the LG Fathom. As of this moment I am only working on the Kernel, where most of the fixes need to be worked on, so let's get to it, shall we?
Download any of the following Android versions:
Gingerbread 2.3.7 (includes Kernel build #119)
DOWNLOAD "einsteinecker_android.rar" (thanks to pizzaboy192 for hosting)
alternate link (untested upload)
What works:
-3G data
-Wifi
-Limited Bluetooth functionality
-Video playback
-3D gaming
-Accelerometer
-Outgoing calls
What doesn't work:
-Camera
-Incoming calls
-SMS
-Vibrator
-Light sensor
-USB
-SD card has a low chance of being mounted.
-
Latest Cyanogenmod Nov 26, 2012
Cyanogenmod with working audio fix, updated link August 28 2013:
Part 1
Part 2
(split into 2 parts because my internet kept cutting it off)
Dead link
Thanks to www2287. Read this post for more info.
-
In some cases, the usual Google apps aren't built into the rom. Read this or this on how to get them.
-
Unsupported Android builds
ajeet's LG Fathom Gingerbread 2.3.7
Download here
What works:
-3G internet!
-Accelerometer!
-Wifi
-Real USB support.
-Outgoing calls
What doesn't work:
-D-pad is not aligned correctly.
-Cannot power off from shutdown menu.
-Incredible power drain. This is caused by the phone remaining at a high mhz without any way to fix it. Even if you use SetCPU to change the governor, the voltage looks like it remains the same so power drains even at 245mhz! :crying:
-No multimedia. And by that I mean no gaming for you, anything 3D is not even enabled on the kernel.
-No camera
-No SMS
-Cannot receive calls
-No light sensor
-No vibrator
Cyanogen Mod
Download here (link thanks to Giorgi-geo)
-
Cyanogen March 2012 build
Download here. from www2287. This build is not a final build, that means many things are broken in it.
-
Android 2.2 Froyo
Download here (NOTE: Due to Froyo not working in some areas, I will not provide support for it)
-
LATEST KERNEL: (March 14 2013)
ReRun March 13 2013: New compiling method to fix several bugs. Read this post for more info.
Previous Kernel:
Rerun kernel build #120
Rerun kernel build #119 (This kernel is a restart of my previous work. I basically started over from scratch and compiled it well over 100 times to find an acceptable solution to the battery issue.)
(Can't type the "." symbol? Download this.)
Kernel source:
https://github.com/ajeet17181/fathom-kernel Note: this source is broken, and since I have heavily modified it, wait for me to upload full source someday.
Booting Android-Now, to use it with one of the above Android versions, first extract the android version into your MicroSD card (You must have at least 750MB free space on your card), and then copy the 3 files inside the kernel archive into the Android folder, overwriting any older files. Next, open startup.txt and make sure the line "rel_path=fathom" has the name of the Android folder in your microSD card, if the folder is "2.2", change "fathom" to 2.2.
-Same as usual, run clrcad.exe about 5 times, then click on "haret" .exe file. The kernel will take a while to boot, so let it sit.
Preparing your phone to enable 3G internet on Android
Now that you have the ROM, you will need to edit your phone to enable 3G internet. Download this: http://www.mediafire.com/?azm89r85x6k2hhz (link thanks to da_reeseboy here.)
Please read the .txt inside the LGNPST archive on how to install. I can't help in that regard as I too funked my install until I undid everything and followed the txt file
After you set that up, download this: https://rapidshare.com/files/606560282/Clipboard01.zip, Or the the texty no frills way:
In windows mobile, change Fathom's USB mode to VZaccess manager mode. Open LGNPST and connect your Fathom. Go to "phone setting" and change default phone mode to GSM, and change the APN setting to the one your carrier uses.
I must warn that Android will attempt to connect when it boots, so be sure you have either an unlimited data plan or make sure you won't be charged if you use prepaid.
Current developments: Next phase of development will focus on the phone side (calls, sms, data). Because I am in a GSM country, I will be focusing on that.
Note: I am quite a busy person, and I won't be updating everyday, at the moment I have a grave matter to handle, and it is my 1TB hard drive. It has corrupt sectors, and it needs to be replaced. It holds crucial XDA data on it, so it is important to me. At the moment I can't afford a new one, so any donations is greatly appreciated in helping me remedy that problem. You can read more about my Hard Drive here.
Changelog
Latest Kernel:
March 14 2013
ReRun New Compile
This kernel was compiled differently than previous kernels, intended to join together the incompatible drivers with the rest of the drivers. This fixed several problems. Read here for more info.
-
November 23, 2012
ReRun kernel build 119
This kernel was restarted from the beginning, and slowly configured to the point where I found a solution to the "connect charger" error on boot. Basically, the kernel source had conflicting power settings combined from the HD2 and Tsunagi sources, and I simply removed the HD2 battery settings and provided a new working source code for the battery. I expect to use this as a base as I further eliminate the invalid .32 codes and replace it with .35 sources.
-
einstein 4x1 (NOTE: read any "readme.txt" files for instructions!!)
-Now, phone will no longer reboot when booting into android. You must make sure your battery level is over 26% in order to avoid this Reboot of Death bug, as it seems like the current build will reset if Android is in a mode where it will warn you to connect your charger. Perhaps we can change Android's low battery notification?
-NVRAM now pointed to /system/etc/wifi/, be sure to root copy the nvram.txt file into the new location.
-(for my modified Gingerbread build) attached are the correct key layouts for the Fathom hardware keyboard (thanks to www2287
Extreme Battery 003
-Re-started kernel development to ensure junk drivers were no longer included. This led to working Wifi, partial bluetooth, fully working headphone support, accelerometer, and as before, no immense power drain on standby. Overnight standby now a reality with Kernel 003!
Extreme Battery 002
Fixes:
-Wifi for Froyo, Bluetooth for Gingerbread
-Accelerometer works for Gingerbread only
-Headphones now work without fail
-Need more feedback regarding resetting while phone is on or off
Extreme Battery 001
Features:
-More CPU governors
-Overclock enabled (use at your own risk!)
-Extreme battery saving (need confirmation, my battery only dropped 2% overnight!)
Working:
-Main speaker
-Phone earpiece
-d-pad now aligned properly
-No more torn screen on the left side!
-Real power-down! Power button is the task manager button beside the camera button. Press this to turn your phone on or off.
Not working:
-Same as before, no outgoing SMS
-Wifi is dead :silly:
-Camera not working
-Never tried GPS...
-When headphones are plugged in, sound dies globally in Android.
Frequently Asked Questions
Where's my microSD card?
It seems strange, but this way worked for me: before you boot into Android, remove the sd card from your phone, then insert it, and then immediately boot into Android. If you did not do this when booting Android for the first time, do this method.
I'm low on storage space.
In "startup.txt", change "data_size=256" to "data_size=512" for 512MB of storage space. If you want more, change 512 to 1024 or 2048 for 1GB / 2GB respectively. Make sure you have that much free space on your MicroSD before you continue!
Can't start Froyo 2.2?
When you see the system process error, immediately press the side button beside the camera, then choose wait, then hold side button, then select power off, and the phone should look like it's booting again, and it should go into Froyo. If it doesn't, repeat again.
Can't boot into Gingerbread 2.3?
Due to a fault in ajeet's battery driver, the OS does not know what the battery life is at boot, and it thinks the battery is dead. Solution? Just make sure you have at least 70% or higher battery life when you boot into Android. I will try to focus on this, but as of the moment, I have not had much success in porting drivers into the kernel, as it is a rather complicated process and it has to be done in a way that will not break the wifi again. (This issue has been fixed in ReRun kernel build 119)
Reserved
Awesome that we have someone working on this again. Slightly curious how hard it would be to port this work over to OpenWebOS... But I'll love to see where Android goes. I'd try using it if the CDMA radio worked.
pizzaboy192 said:
Awesome that we have someone working on this again. Slightly curious how hard it would be to port this work over to OpenWebOS... But I'll love to see where Android goes. I'd try using it if the CDMA radio worked.
Click to expand...
Click to collapse
I'm optimistic CDMA would work, that unfortunately might need to have the Android OS edited to support dual mode CDMA/GSM. A nice place to start would be the Android builds for the Touch Pro2.
einsteinecker said:
I'm optimistic CDMA would work, that unfortunately might need to have the Android OS edited to support dual mode CDMA/GSM. A nice place to start would be the Android builds for the Touch Pro2.
Click to expand...
Click to collapse
We should also see what other Android-only devices used the same modems. The Droid series usually were world devices, as were a few others (none off the top of my head, but I bet they're pretty easy to find)
Worst case scenario would be to compile two different Android versions that are either CDMA only or GSM only.
I've got 3 Fathoms to test on, and would be more than willing to sell my unlocked one to someone who could use it better than I could (it's currently de-activated and I don't have a GSM SIM to test.
nice! thanks for your work einsteinecker
so here's my problem. i did everything as said. HTC logo comes on and that's it. i waited for 40+ minutes for it to load but nothing
edit: never mind. On the third try it loaded correctly
---------- Post added at 09:38 PM ---------- Previous post was at 09:00 PM ----------
-No more torn screen on the left side!
-Real power-down! Power button is the task manager button beside the camera button. Press this to turn your phone on or off.
Click to expand...
Click to collapse
love you. please fix wi-fi soon )
---------- Post added at 09:44 PM ---------- Previous post was at 09:38 PM ----------
i was using 2.3.1 android before this. now i installed 2.2 and the difference in performance is huge. 2.2 is much faster and smoother on our device. can you tell me what is the key difference between 2.3.1 and 2.2? if there is none I think it will be better to have 2.2
forget this too. looks like both build work better with your help )
Also. when in android, and i connect USB and transfer some files onto sdcard. they dont show up in file manager until reboot, and sometimes they just disappear. this is happening since first ajeet build - not a new problem, but maybe you could look into it.
---------- Post added at 02:47 AM ---------- Previous post was at 02:36 AM ----------
Not working:
-Same as before, no outgoing SMS
-Wifi is dead :silly:
-Camera not working
-Never tried GPS...
-When headphones are plugged in, sound dies globally in Android.
Click to expand...
Click to collapse
bluetooth also does not work )
Sorry folks, I meant to update yesterday but I had a mind crushing headache
pizzaboy192 said:
We should also see what other Android-only devices used the same modems. The Droid series usually were world devices, as were a few others (none off the top of my head, but I bet they're pretty easy to find)
Worst case scenario would be to compile two different Android versions that are either CDMA only or GSM only.
Click to expand...
Click to collapse
I recall most Droids from Motorola have the OMAP cpu, so I'm not sure if using the code for that would work on our Qualcomm stuff (I believe LG used a Qualcomm reference guide for the Fathom). I figured checking Qualcomm's sources first is a good try.
I've got 3 Fathoms to test on, and would be more than willing to sell my unlocked one to someone who could use it better than I could (it's currently de-activated and I don't have a GSM SIM to test.
Click to expand...
Click to collapse
I've been interested in something. How is android on the newer updates? What I mean is that, I'm still running stock V4 Windows Mobile ROM on my Fathom, and there is no performance lock like on the HTC HD2 (full 1Ghz on battery). Does the V5 or V7 WM Roms have this too?
Giorgi-geo said:
i was using 2.3.1 android before this. now i installed 2.2 and the difference in performance is huge. 2.2 is much faster and smoother on our device. can you tell me what is the key difference between 2.3.1 and 2.2? if there is none I think it will be better to have 2.2
forget this too. looks like both build work better with your help )
Click to expand...
Click to collapse
One main difference I see between 2.2 and 2.3, is that 2.3 rotates the screen immediately after you slide out the keyboard. 2.2 will only rotate once you open a program.
Giorgi-geo said:
Also. when in android, and i connect USB and transfer some files onto sdcard. they dont show up in file manager until reboot, and sometimes they just disappear. this is happening since first ajeet build - not a new problem, but maybe you could look into it.
Click to expand...
Click to collapse
If you read the readme text file inside the 2.2 Android build, you'll see it's a problem of the OS:
"- USB Mass Storage (You can copy files from PC to PC. But Android apps cannot see the copied files in the phone before rebooting.)"
I think that is because we run Android from our SD card.
bluetooth also does not work )
Click to expand...
Click to collapse
Thanks for the feedback. I was going to upload the headphone fix yesterday, but maybe I'll try that bluetooth fix too.
einsteinecker said:
I recall most Droids from Motorola have the OMAP cpu, so I'm not sure if using the code for that would work on our Qualcomm stuff (I believe LG used a Qualcomm reference guide for the Fathom). I figured checking Qualcomm's sources first is a good try.
I've been interested in something. How is android on the newer updates? What I mean is that, I'm still running stock V4 Windows Mobile ROM on my Fathom, and there is no performance lock like on the HTC HD2 (full 1Ghz on battery). Does the V5 or V7 WM Roms have this too?
Click to expand...
Click to collapse
I am not sure what the differences between the OMAP refrence and the Qualcomm refrence designs are. I know the Fathom is a 1ghz Snapdragon, but not sure what else it has in it.
Also, what do you mean by performance lock? I run my own ROM (V6) and it seems to run well. I don't do OC, but I have successfully underclocked the device to 215mhz (somewhere around there) as a test and it was stable. Eeked almost two weeks of battery out of a test device that way.
maybe you could fix wi-fi too? it was working before, so if you could compare the code you could probably fix it fast.
---------- Post added at 12:42 PM ---------- Previous post was at 12:19 PM ----------
one more thing. in android it only shows 165mb ram
---------- Post added at 12:54 PM ---------- Previous post was at 12:42 PM ----------
IMPORTANT: when going back to Windows Mobile, do not, I repeat DO NOT reset the phone while Android is off (screen off, standby). Make sure Android is on before you go back into Windows Mobile, if you don't, Android will be locked into an eternal "off" state, and you will never be able to go back into Android again.
Click to expand...
Click to collapse
I think this just happened to me. every time i load android it goes to unlock screen and then turns off. i always turned android off from its own menu so i dont know why it happened. there has to be a way to fix this, help please?
---------- Post added at 01:46 PM ---------- Previous post was at 12:54 PM ----------
after 5 tries, i connected phone with charger and on the second try it turned on
Hi folks, after my previous build work for headphones and not Bluetooth, I tried fixing Bluetooth but now the headphone port is wonky :silly:
While that was happening, I found out why Wifi wasn't working. Now, on 2.3 Gingerbread Wifi doesn't work (probably firmware problem), but in 2.2 Froyo it does work, but can't find any networks
That's when I was trying to fix things on the Android side (not the kernel) when I apparently got one thing to partially work:
I hope you noticed the 3G icon on the top, yes it's very close to working, the only problem I've got is making the phone realize that there is a sim in there (and the outgoing number to dial). Now, 2.3 Gingerbread can see the sim, so I'm going to try that, but if this works, I think we're in for a heck of a ride
Once I have both headphone and Bluetooth support stabilized, I will upload that. The 3G and Wifi fixes involve the Android OS itself, so that means I have to uploaded the OS or give instructions how to patch them in yourself.
pizzaboy192 said:
I am not sure what the differences between the OMAP refrence and the Qualcomm refrence designs are. I know the Fathom is a 1ghz Snapdragon, but not sure what else it has in it.
Click to expand...
Click to collapse
Well I certainly won't rule anything out. Right now any thing is a good thing to test, who knows, maybe the Droid actually has what I'm looking for
Also, what do you mean by performance lock? I run my own ROM (V6) and it seems to run well. I don't do OC, but I have successfully underclocked the device to 215mhz (somewhere around there) as a test and it was stable. Eeked almost two weeks of battery out of a test device that way.
Click to expand...
Click to collapse
Performance lock is like this: when I had the HD2, while on battery (no AC plugged in) the phone will have only a maximum speed of 768Mhz. My Fathom does not have this, it is a max 1Ghz on battery and on AC. What I'm wondering is, maybe LG's V5/V6/V7 updates changed something, I'm not sure. I sure don't want to risk my only phone either, and there's more: what if all this time LG's updates also updated the phone baseband. So while I'm porting Android to our phones, maybe my updates won't work with the old V4 I'm running. There certainly is a lot of things to consider when doing this stuff :silly:
Giorgi-geo said:
I think this just happened to me. every time i load android it goes to unlock screen and then turns off. i always turned android off from its own menu so i dont know why it happened. there has to be a way to fix this, help please?
Click to expand...
Click to collapse
I think there might be a way to fix this, unfortunately I have had little succes porting drivers over to my kernel. It is one of the reasons why I can't get the camera to work yet, porting drivers is not as simple as copying and pasting drivers like in windows mobile.
But I think it could work, you see, my idea was to tell Android that there's a reset button onboard the phone (the one beside the charging port). LG has the code for this, which I was able to see, but haven't been able to get working yet.
Edit: Wifi is still dead on 2.3 Gingerbread, but I fixed the Accelerometer :victory:
Couldn't test Froyo because I broke the Android build, will redo and continue further tests
Awesome work! I'll run some tests on my end with the CDMA half if you'd like and report back to see what is and isn't working connectivity wise there.
As for the WiFi half: is it getting an IP address? Can you check the DNS settings to make sure they are being set properly?
As for the performance lock: none that I know of.
And as for the question about baseband: No baseband differences between ROM versions. They're purely a WinMO flash, and not a BaseBand flash. If you'd like, I can run tests on all 3 OEM versions of the ROM though, as I have 3 unused Fathoms, all on different ROM versions currently. I've even tried cooking a WinMo ROM that autoboots into Android (almost works, tempted to just put a HaRET shortcut in startup and strip out all WinMO core programs.
Froyo doesn't like my kernel anymore, even tried a different SD card and it still has a system crash on boot. I guess it's time to work on a new OS :crying:
pizzaboy192 said:
As for the WiFi half: is it getting an IP address? Can you check the DNS settings to make sure they are being set properly?
Click to expand...
Click to collapse
It's just scanning, it won't even find the network
And as for the question about baseband: No baseband differences between ROM versions. They're purely a WinMO flash, and not a BaseBand flash. If you'd like, I can run tests on all 3 OEM versions of the ROM though, as I have 3 unused Fathoms, all on different ROM versions currently. I've even tried cooking a WinMo ROM that autoboots into Android (almost works, tempted to just put a HaRET shortcut in startup and strip out all WinMO core programs.
Click to expand...
Click to collapse
Oh, that's what I wanted to know, if the LG updates include a radio update. I'm highly interested in knowing if there will be better performance in Android if they updated the radio.
einsteinecker said:
Oh, that's what I wanted to know, if the LG updates include a radio update. I'm highly interested in knowing if there will be better performance in Android if they updated the radio.
Click to expand...
Click to collapse
We could also see what other devices used the same radio chip. I know that plenty of them are out there, it's just a matter of finding one that will provide an updated baseband and see how badly it screws up the phone (since we don't have the OEM baseband, doing that would probably brick any device you modded, if it went wrong)
How are you doing your work? any possibility of throwing it on some place like github so that people like me can try out changes and put our own in to help out? I have a test fleet just sitting doing nothing since I can't get much more out of Windows Mobile and cooking ROMs has gotten rather repetitive.
pizzaboy192 said:
We could also see what other devices used the same radio chip. I know that plenty of them are out there, it's just a matter of finding one that will provide an updated baseband and see how badly it screws up the phone (since we don't have the OEM baseband, doing that would probably brick any device you modded, if it went wrong)
How are you doing your work? any possibility of throwing it on some place like github so that people like me can try out changes and put our own in to help out? I have a test fleet just sitting doing nothing since I can't get much more out of Windows Mobile and cooking ROMs has gotten rather repetitive.
Click to expand...
Click to collapse
The kernel source is in the first post That's all I'm doing now, I get discouraged when I see the steps I have to take to make the Android OS, neither ajeet or www27 uploaded that and it's going to be a lot to download (I have limited bandwidth) What I've been doing is modifying Android while it's running (root access), and that's how I applied the accelerometer and that 3G thing.
Tomorrow I will upload the latest fix, which includes:
-bluetooth support (paired with headset and able to receive files)
-headphone support fixed
-how-to for the accelerometer (I will add a game so you can test it )
I'm currently prioritizing 3 things: why the SD card doesn't always mount on boot, charging the phone while using Android, and why my kernel doesn't like Froyo and the fixes that used to work.
einsteinecker said:
I'm currently prioritizing 3 things: why the SD card doesn't always mount on boot, charging the phone while using Android, and why my kernel doesn't like Froyo and the fixes that used to work.
Click to expand...
Click to collapse
what's wrong with charging? i dont see any problems
Random question: any way to get the Android main to boot off the internal flash? if so, I could build "ROMs" that boot WinMo and immediately start HaRET and handoff to Android. I tried earlier, but ended up with a failed boot every time.
Related
Folks,
I'm starting this new thread since the release one is getting way too big to manager.
Please start posting issues related to my rom here, make sure they are actual issues and not user error.
Regards,
Windows Live / Hotmail Problems
Does anyone else have problems getting Windows Live to sync your hotmail? I finally got it working with the push support, but it does not allow me to download attachments. Anytime I try to download an attachment it says failed to sync. I've tried the 3 latest versions available from this board and none of them seem to work. I've also tried these combinations with both versions of biggy 4.0 to no avail. With open touch 3.0 (Windows live biggie) the Windows Live service was working perfectly. I can't imagine that having windows live built into the Rom was what made the difference. Any one have any ideas? If this is simply an unfixable bug do you know if the gmail imap works like a push client? I tried to configure gmail, but it wouldn't allow anything quicker than a check every 5 mins.
Once again thanks ttran for your hard work in creating this great rom. Without it I'd probably be an iSheep by now.
thanks in advance
Not sure if this is an operator error or the rom error but I installed the Black Dialer from this link http://forum.xda-developers.com/showpost.php?p=1649317&postcount=1
I followed the instructions and did a soft reset, after that the Micro v4.1 run really sloooow. I have to perform a hard reset and reinstall all the other cabs.
So is it because I installed the wrong dialer cab or is it something wrong with the Micro v4.1? Whatever reason is I hope this is a good info for other ppl, too.
Other than that the Micro v4.1 run amazing fast and I do miss the black dial from the Lite Black version
when i added the battery to my toolbar and decided to take it off, the taskmanager that was up there disappeared, i cant get it back
djkdawg said:
when i added the battery to my toolbar and decided to take it off, the taskmanager that was up there disappeared, i cant get it back
Click to expand...
Click to collapse
I was all ready to get mad....break out the flamethowers and what not, but after testing this is CONFIRMED. I added percent and mem feedback to the screen using QM, removed them and could not reenable htc task mgr. I want to say there used to be an option in the HTC x-button settings to show on today screen. That option is not there. Currently searching for the reg key.... will update post
high pitch noise comming from the speaker after flashing the rom
pixelwix said:
high pitch noise comming from the speaker after flashing the rom
Click to expand...
Click to collapse
Using battery status?? I get the noise while using the cpu scaler UNDERclocking below 149. If it annoys you that much raise your min to 149. Otherwise, just try setting different processor speeds...dont over do it, see if that doesnt help.
ttran...I finally resolved my problem with Pocket Nester! Turns out it was user error... I had the files on my storage card in My Documents instead of having them at the root level. I noticed that it was seeing some of the folders on the storage card but none of the ones in My Documents. I moved them to the root of the storage card and it works!
since there is talk about the dialer i thought i would ask... in OT Biggy 3.0 the dialer had buttons that were quite large.
in this version the dialer is alot better, because it has the contacts built right into it at the top. however there is alot of space between the buttons, making them too small for my fingers.
is there a skin that just makes the dialer buttons bigger without downgrading back to the 3.0 version?
great work ttran, i am running 4.0 biggy w/ cube... just fyi and no issues thus far (only been testing for 2 days though)
Radio issue?
I'm not sure if this is a radio issue or something else, but here goes.
I flashed the lite black rom late last week.
I've been running a BT GPS for a while now with this phone. I've had my BT headset paired as well. I can use both at the same time. Monday, while talking on the headset, it just ended the call spontaneously. A few minutes later, after getting a call back on, it just ended the BT portion, and I had to actually pick up the phone (Horrors!)
Today, the cell phone side seems to be having troubles. (I've not tried the BT headset again, but still running the GPS) Several times I have had a "!" next to the phone icon in place of a signal strength meter... no signal or some error. I've had connection errors with the GPRS as well.
I may try out the micro with the newer radio in it, or look more into flashing an older radio version on here.
Let me know if you need any more details.
dirtisgood said:
I'm not sure if this is a radio issue or something else, but here goes.
I flashed the lite black rom late last week.
I've been running a BT GPS for a while now with this phone. I've had my BT headset paired as well. I can use both at the same time. Monday, while talking on the headset, it just ended the call spontaneously. A few minutes later, after getting a call back on, it just ended the BT portion, and I had to actually pick up the phone (Horrors!)
Today, the cell phone side seems to be having troubles. (I've not tried the BT headset again, but still running the GPS) Several times I have had a "!" next to the phone icon in place of a signal strength meter... no signal or some error. I've had connection errors with the GPRS as well.
I may try out the micro with the newer radio in it, or look more into flashing an older radio version on here.
Let me know if you need any more details.
Click to expand...
Click to collapse
Hi,
I'm aware of the issues with the current radio, that why I posted the old radio and splash from v3.0.
Please go back to the first page of the actual release page for v4.0 to download it.
joking said:
Not sure if this is an operator error or the rom error but I installed the Black Dialer from this link http://forum.xda-developers.com/showpost.php?p=1649317&postcount=1
I followed the instructions and did a soft reset, after that the Micro v4.1 run really sloooow. I have to perform a hard reset and reinstall all the other cabs.
So is it because I installed the wrong dialer cab or is it something wrong with the Micro v4.1? Whatever reason is I hope this is a good info for other ppl, too.
Other than that the Micro v4.1 run amazing fast and I do miss the black dial from the Lite Black version
Click to expand...
Click to collapse
The dialer I used for v4.0 is different than any others. I did not include it in the micro since there are so many people with different wants and needs.
Some dont like the color of the dialer, some don't like the way the buttons are too small, and etc.
Thus I just plan left it out, so you the user can install a different dialer on top of the existing one.
But I think the one you try to use does not work correctly as a cab.
I've tested the micro version by installing different dialers with success.
I will try and locate a similar dilaer to mine or just create a cab for you folks as soon as I get some free time.
I still need to post different colors for the back ground as well.
Been busy working on my personal rom which will be for version 5.0 and the other versions of 4.0.
i'm using OT 4.0 biggy vista and everytime I set the backlight option to turn off after 3 minutes instead of 30 seconds and the power to turn off in 5 minutes instead of 2 as soon as the power goes off and I turn it on it's right back to 30 seconds and 2 minutes. This ain't a major issue it's just a pain in the ass cuz i'm using slide to unlock and evry 30 seconds I have to keep unlocking it.
nextpimp said:
I was all ready to get mad....break out the flamethowers and what not, but after testing this is CONFIRMED. I added percent and mem feedback to the screen using QM, removed them and could not reenable htc task mgr. I want to say there used to be an option in the HTC x-button settings to show on today screen. That option is not there. Currently searching for the reg key.... will update post
Click to expand...
Click to collapse
I personally like it that way better, That way the HTC task manager and the OK button dont overlap and creat confusion. Instead, I use Quickmenu since that has it's own task manager. It shows you what's running and you can close them as well using Quickmenu.
Take a look into it
ttran001 said:
Been busy working on my personal rom which will be for version 5.0 and the other versions of 4.0.
Click to expand...
Click to collapse
I'm more then willing to Beta test 5.0 when ready let me know!
nKiwan said:
I'm more then willing to Beta test 5.0 when ready let me know!
Click to expand...
Click to collapse
I'm game too.
ttran001 said:
The dialer I used for v4.0 is different than any others. I did not include it in the micro since there are so many people with different wants and needs.
Some dont like the color of the dialer, some don't like the way the buttons are too small, and etc.
Thus I just plan left it out, so you the user can install a different dialer on top of the existing one.
But I think the one you try to use does not work correctly as a cab.
I've tested the micro version by installing different dialers with success.
I will try and locate a similar dilaer to mine or just create a cab for you folks as soon as I get some free time.
I still need to post different colors for the back ground as well.
Been busy working on my personal rom which will be for version 5.0 and the other versions of 4.0.
Click to expand...
Click to collapse
Yes you're right. I had to hard reset the Wing since that Black dialer doesn't have the removed option. Well it's a learning experience for me too. And fortunately that v4.1 is UC, all I need to do is remove those cabs from the SDConfig.txt file and re-run it again and voila all the cabs I need is back on the Wing.
Can't wait till you post the cab for the dialer.
So far I love the Lite Black but I like the speed on the Micro better. That's why I try to get the Micro as much closer to the Lite Black as possible.
1 more thing I notice on the Micro, after installed "JUVS HTC Home.v2_1_1005722_s0" cab sometime when I switch back to the home the area where the HTC Home should be got "scramble" for about 2 sec. I still try to duplicate it and report back. It already happened to me 2 times today.
now people have to read 2 threads for 1 rom....... mhhhhhhh.
Just can say Thanks for your great rom.!
It runs perfect..
papamopps said:
now people have to read 2 threads for 1 rom....... mhhhhhhh.
Click to expand...
Click to collapse
This is why "Tab browser" kick in
Froyo NAND ROM for Flytouch2 by Stragulus
Video demonstrating how to flash the tablet after having created the bootable SD-card: http://www.youtube.com/watch?v=47kf4-Vbba8#t=3
RELEASE NOTES
Please provide feedback if things work, or do not work for you.
If it eats your tablet, don't blame me. I deem it low-risk though, if it fails you can reflash it using burntool or another bootable sd-card just like before.
INSTALLATION
Installation is slightly different from normal releases because it requires flashing in 2 steps. Luckily, it's really easy:
1. Download bootable SD-card image and unzip: http://www.mediafire.com/?4quqzqyce9eje7a
2. Write image to an SD-card that's at least 1GB in size using WinHex:
Get WinHex here: http://www.winhex.com/winhex/
In WinHex: tools, disk tools, clone disk
Choose file from zip (sdcard.img)
Choose the sd card as your destination
Start sector: fill in 0, also make sure the directories are correct on left
When finished, take out the card.
In linux, you just unzip the file and use dd to write it to the sd-card:
Code:
dd if=/path/to/sdcard.img of=/dev/sdX # (where sdX is your scsi disk device, check dmesg)
3. Turn off tablet and put sd-card in TOP slot (between the 2 usb ports).
4. Turn on tablet. It will report that it is booting off the sd-card, and that it's flashing kernel + filesystems.
5. Take out the sd-card when the tablet asks you to do so (takes less than a minute). Put it in the OTHER sd-card slot (bottom one), and reboot the tablet by holding down the power for 10 seconds to turn it off, then press it again to turn it on.
6. You will now see the tablet booting with a *GREEN* screen. The screen will flash twice to indicate it's starting. The flashing itself will take longer than in the previous step, a few minutes. If succesful, it will automatically reboot, after which you're done and you're booting the new firmware! You'll see a different boot screen (equalizer on a black background)
7. After it has booted and you have unlocked the screen, reboot the tablet first thing! First boots in android always tend to be behave erratically. This is unrelated to this firmware and applies to all Android setups.
If step 6 fails (which is very unlikely), it will stay on the green screen and it will keep on flashing the screen. In that case, you'll have to turn it off. Most likely problem for this is a corrupt SD-card. See troubleshooting below.
Make sure to never put that sd-card back in the top-slot without erasing it first, as it will reflash your tablet!
TROUBLESHOOTING
The 'green screen' keeps flashing!
The installer will dump a text file on the root of the sd-card which you can inspect. The file is called fail_reason.txt. If no such file exists, things are seriously wrong and the tablet couldn't even properly write to the sd-card. If using another SD-card, or rewriting the SD-card doesn't help, please upload the fail_reason.txt file here.
Flashing was succesful, but the system doesn't boot up!
The installer dumps one or more text files on the root of your sd-card during the 'green screen' flashing stage. Upload all these files and link to them here.
TODO
Find out why some users can't get past the android boot animation despite seemingly succesful flashing
Rewrite instructions for creating the sdcard @ windows
Figure out why Titanium Backup doesn't work
(**) Tested:
wifi, ethernet port
battery status works, g-sensor works
touchscreen works (precalibrated, you cannot recalibrate it using the settings app)
HD video playback works (I recommend Meridian player)
Market works (full)
angry birds works ( thought I'd mention it )
The firmware has already been rooted! You can connect using adb over wifi, and type 'su' to become root. Find your IP address using the Android System Info app.
GPS confirmed
Tablet details:
CPU: InfoTM IMAPX220 1GHz CPU ARM1136
Display: 10.2” (WXVGA 1024×600 ) LCD (26M)
RAM: 256MB DDR2 / ROM: 2GB
Camera: 1.3M
GPS: HopeRF XN203
Wifi: AzureWave 802.11B/G
Battery: 3800mah
Adapter: 9V 2/5A
2x USB
1x RJ45
1x HDMI
2x MicroSD
1x Stylus-slot
- Vibration
- Accelerometer
Dimension: 269.91mm*170.45mm*14.89mm 700gr
Buttons: Back, Home, Menu, Volume, Wifi, Reset and Power
Also known as
- FlyTouch II
- SuperPAD
- WOWpad
- WWE10
- PC1002I
- HyPE-Pad
- ZH10X2
- APad GF10
- CEM111
- Daystar MD10
- Careeror CM10104
Is it really a 1ghz cpu this time?
Cause, i heard it was only 800mhz and wasn't cortex a8
flyboyovyick said:
Is it really a 1ghz cpu this time?
Click to expand...
Click to collapse
You can look up the specs here.
Just got one yesterday, and so far I would say it is a very nice unit.
Everything is very responsive compared to other android tablets I have tried.
The book reader is very nice, and the video player is great. Played a 900mb divx movie without a hitch.
Market works good on this unit also.
My only problem is that when I try to run the system update.apk that came on the unit it asks for a license. A 20 digit code. If I select register later it will not allow for update check because it says it is an unincorporated device.
Like I said earlier market works fine, have downloaded several apps.
I even tried the market fix for the Zenithink ZT-180 from this forum hoping if I inserted a new androidID I could check for updates. No luck.
Any ideas?
Do you know where I can find updates and roms for this unit on the internet?
I got the system update.apk from the root and thought maybe I could check somehow where it was pointing the tablet to look for the updates. Is this possible?
I am currently running dory-r2.1.925 and kernel 2.6.32.9 [email protected] #1
cjadams51 said:
Just got one yesterday, and so far I would say it is a very nice unit.
Click to expand...
Click to collapse
Nice to hear! Your problem with the license-code is a known issue, many people have that problem. Just ignore for it now, the manufacturer said their will be a new ROM which doesn't ask for it.
Thanks for providing a resource for this machine.
Will the rom updates be posted here when they are made available or can you direct me to the manufacturers website, as I can not update via the system update app?
ROM's will be posted here, but those websites are:
Gome www.gome.com.cn
InfoTM www.infotmic.com.cn
As soon as there is a new ROM, i will update this topic.
Just ordered one. I sent back my broken ZT-180 and they are sending me a discounted FT2. A few questions:
1) The ZT-180 didn't have a true sleep mode. Does this?
2) The ZT-180 only has a 3-Axis accelerometer, making it useless for apps and games that use the g-sensor (it just has screen rotation). How's this one?
3) How's the battery compare? The last one was terrible.
4) Does it seem faster? Slower? Same?
Zap! said:
1) The ZT-180 didn't have a true sleep mode. Does this?
Click to expand...
Click to collapse
I am not sure. I haven't received mine yet.
Zap! said:
2) The ZT-180 only has a 3-Axis accelerometer, making it useless for apps and games that use the g-sensor (it just has screen rotation). How's this one?
Click to expand...
Click to collapse
I believe its the same (also also 3-Axis).
Zap! said:
3) How's the battery compare? The last one was terrible.
Click to expand...
Click to collapse
ZT-180 has 2000mAH, this one has 3800mAh, so it's almost double!
Zap! said:
4) Does it seem faster? Slower? Same?
Click to expand...
Click to collapse
Exactly the same CPU speed.
Drazix said:
I am not sure. I haven't received mine yet.
I believe its the same (also also 3-Axis).
ZT-180 has 2000mAH, this one has 3800mAh, so it's almost double!
Exactly the same CPU speed.
Click to expand...
Click to collapse
Hmm, really hope the accelerometer works in games and it has a sleep mode. Lemme know when you get it please.
Zap! said:
Lemme know when you get it please.
Click to expand...
Click to collapse
It's already shipped, so I get it in 3 days. But maybe 'cjadams51' can provide this info sooner.
It's a bit of an odyssey to order one here in Germany, but I started collecting material and info related to the FlyTouch2:
onderka.com/inhalt/gome-flytouch2-android-tablet/
The system/board-codename is "Emma", and I'm so curious how development of this thingy will turn out.
On this site that sells the FT2, I asked the following and got answers:
Does the g-sensor work in games, or does it just have auto-rotation?
Does it have a sleep mode?
Administrator yes, it can play g-sensor games.
yes, it has sleep mode also.
Thanks
Click to expand...
Click to collapse
That's strange, because the same page lists the following specification:
gravity sensor
3 direction
Click to expand...
Click to collapse
And 3 axes = no games
Anyone got some informations about of there will be a constant firmware improve like the zt-180? And if there maybe release the code
Gsensor works fine in the game labyrith. The screen however when playing this game does not display in full screen mode, only about quarter screen. I assume because it was designed for phone, but gsensor seems as responsive as playing it on my phone. The only draw back to the tablet so far is the battery life could definitely be better. I have not messed with gps that much. I am also trying to get it to work with my 3g mobile broadband card. I have a 595u card from sprint. Would love to be able to plug into usb and have internet on the go.
Any suggestions to get this going. When I plug in it is not reconized in the 3g settings.
Really enjoying ebook reader and movie player.
Not sure what you mean by true sleep mode. It does seem to go to sleep (screen turns off) when inactive.
In fact using it now on wifi to browse this forum hoping for rom update.
Drazix said:
That's strange, because the same page lists the following specification:
And 3 axes = no games
Click to expand...
Click to collapse
cjadams51 said:
Gsensor works fine in the game labyrith. The screen however when playing this game does not display in full screen mode, only about quarter screen. I assume because it was designed for phone, but gsensor seems as responsive as playing it on my phone. The only draw back to the tablet so far is the battery life could definitely be better. I have not messed with gps that much. I am also trying to get it to work with my 3g mobile broadband card. I have a 595u card from sprint. Would love to be able to plug into usb and have internet on the go.
Any suggestions to get this going. When I plug in it is not reconized in the 3g settings.
Really enjoying ebook reader and movie player.
Not sure what you mean by true sleep mode. It does seem to go to sleep (screen turns off) when inactive.
In fact using it now on wifi to browse this forum hoping for rom update.
Click to expand...
Click to collapse
Well, that could only mean one of two things:
1) It's incorrectly listed as 3-axis.
2) It is what I've suspected all along. That Zenithink, with their 3-axis ZT-180, got it wrong when they blamed it on the g-sensor. The ZT-180 can indeed make use of the g-sensor in games, it's just Zenithink's incompetence that's holding it back.
As for true sleep, the ZT-180 doesn't have one. When it times out, the screen goes darker but there's still some light. It never goes totally black unless the unit is powered off, or dead.
Zap!: It's not one of two things, it must be both things
cjadams51: Can you tell more about the battery life? How many hours can you use it?
Drazix said:
Zap!: It's not one of two things, it must be both things
cjadams51: Can you tell more about the battery life? How many hours can you use it?
Click to expand...
Click to collapse
The battery life varies of course depending on what your doing. w/ wifi on and surfing maybe 1.5 - 2 hours. As an ebook reader with no wifi over 2 hours.
I am also noticing that the battery gauge is a little sporadic and does not seem always be dependable or accurate. I need to install a battery info app, so I can get a better idea.
The gauge currently reminds me of sometimes when I install a new rom on my mt3g the battery guage seems to be sporadic before it settles down and becomes a more reliable. Still getting a feel for it. It could also be that I am using a little more than I think, I just know that I've gotten hit with the 15% battery warning several times, and it seems like I had not been using it that much.
This is posted over in the DHD sub-forum but I didn't find any reference to it over here... stands to reason many may not know about it.
Part of the reason we are getting such low battery life on CM7 may be due to the aic3254 chip not turning off properly when its not being used.
mad-murdock has posted a flashable zip that contains a slightly modified kernel ("just the driver for the AIC3254 dsp chip is changed") along with some DSP related stuff that addresses and corrects this issue.
I personally flashed this on top of CM Nightly 14 after doing a no-wipe (did wipe cache and dav cache of course) upgrade from Nightly 8 + audio/gps fix.
The author of this fix has said:
note: after using phone for any calls, power down is disabled again. usual voice search enables it again.
So although originally it was thought that Version 5 no longer requires Google's voice search or voice dialer to be used once after every reboot to correctly initialize the fix, as you can see, you need to use google voice services after each phone call* to correctly initialize the power management of the chip
Once you have done that, the result of entering the command:
Code:
# aic3254pd status
from terminal emulator on the phone, or:
Code:
adb shell aic3254pd status
from a command line on your PC should give you this:
Code:
Power status of aic3254 chip: OFF
Please note as of this late hour, I'm not sure how this interacts with the changes made to the Inspire 4G kernel. I realize that as of CM7 RC2 there is a Unified kernel in place that handles the audio fix automatically, I do not know if mm's kernel is using that fix or not. I was however able to call my voice mail and leave a message and successfully play it back via google voice.
Use at your own risk, don't blame me, etc etc.
Please report back and let me know both how it affects battery life and whether or not audio quality is adversely impacted.
DOWNLOAD:
Version 5 md5: f7c7b01a47266b26b8a01f2fc853cfbe mirror mirror
more information can be found over in the original thread in the DHD sub-forum
Thanks again to Mad-Murdock for his continuing hard work on this.
*Radio Update Info
Personal tests have shown that after updating the radio, the Voice search only has to be used once after the first call, not after each additional call. This works for me, but I can't guarantee it will work for everyone.
Before Updating your Radio, make sure you are BOTH Radio S-OFF and ENG S-OFF
The Radio I'm using (the Author of the fix is using it as well):
28th January 2011: Radio_12.35d.60.140f_26.06.03.24_M2 - TELUS WWE 1.84.661.1
MD5 Checksum: edc9b36f3e30b8a3aec0f8e5ebfe9484
I haven't had any battery drain with cm7...
HTC Inspire Clockwork Recovery * CM7(kang) * Eng S-Off
BelacNongaw said:
I haven't had any battery drain with cm7...
HTC Inspire Clockwork Recovery * CM7(kang) * Eng S-Off
Click to expand...
Click to collapse
For me CoreDroid on average with the screen off drains 4-8mah, CM7 build 13 is draining 15-100+ . mah
First post updated to contain fix #5
running the command returns that the chip is ON until you run the voice dialer. i used fix 5, flashed over cm7 rc2. obviously, the fix is still broken.
edit;
can verify the fix works once you do run the google voice dialer, pulling 9ma with screen off, before running the voice dialer im pulling 263ma. something is seriously wrong with this mod, glad it's been found, eagerly awaiting a working fix.
edit again;
was something changed with the wifi aswell? im getting full bars when pre-flash i was getting two. sitting in the same chair and haven't moved before during or after the update, so it's not that.
Let's get this pushed into the next nightly.
let's not push this into the nightly until we don't have to keep running google voice to make it work, please? forgetting to do that could ruin your day if you leave your charger at home. :/
fwayfarer said:
let's not push this into the nightly until we don't have to keep running google voice to make it work, please? forgetting to do that could ruin your day if you leave your charger at home. :/
Click to expand...
Click to collapse
You should read the update. #5 does not require the workaround.
What type of draws are you guys seeing? With the patch installed and airplane mode on i'm still seeing a 10mA draw, 18mA with radio on.
you should do some real world testing. do you even run the rom?
i flashed to cm7 rc2, and installed fix 5 as linked above, and running the status command in terminal reports the chip as ON until i run the voice dialer, then it reports the chip as OFF.
did you even read my post?
with the screen off, radio and wifi on i am seeing 9ma draw as reported by battery monitor widget from the market.
fwayfarer said:
you should do some real world testing. do you even run the rom?
i flashed to cm7 rc2, and installed fix 5 as linked above, and running the status command in terminal reports the chip as ON until i run the voice dialer, then it reports the chip as OFF.
did you even read my post?
with the screen off, radio and wifi on i am seeing 9ma draw as reported by battery monitor widget from the market.
Click to expand...
Click to collapse
I've been running the rom for weeks and have tested the newest patch with google voice uninstalled. It works perfectly. This is with RC2 and nightly 14.
removed......
mentalcase said:
I've been running the rom for weeks and have tested the newest patch with google voice uninstalled. It works perfectly. This is with RC2 and nightly 14.
Click to expand...
Click to collapse
welp, read the updated op. looks like voice is still needed.
fwayfarer said:
welp, read the updated op. looks like voice is still needed.
Click to expand...
Click to collapse
I'm not sure where the OP is getting their info from, but the original post over in the dhd section has not been updated and still maintains that voice apps are not needed. Also, no one has posted in that thread since 5 was released to say that there is an issue.
http://forum.xda-developers.com/showpost.php?p=11919563&postcount=1
Edit: Looks like there is an issue on some radios where the chip doesn't turn off automatically after a phone call. I've noticed that if i reboot the chip is off automatically, but after a phone call the voice dial method is needed to turn it back off or a reboot of course. We may have to flash a different radio version to get this to work.
do we know what the offending radio versions are, and what are known good versions? id like to fix this asap, i dont really want to go back to revo, but it was pretty solid compared to all these bugs with cm7.
mentalcase said:
I'm not sure where the OP is getting their info from
Click to expand...
Click to collapse
From the author of the fix. See instead of just reading the first post over there, I read the entire thread (something I would recommend to anyone before posting an uninformed comment that insinuates I don't know what I'm talking about.)
On page 11 I found this:
mad-murdock said:
note: after using phone for any calls, power down is disabled again. usual voice search enables it again.
not sure how to bypass this yet. needs further investigation tomorrow. good night
Swyped with cyanogenmod 7 powered HTC Desire HD. Excuse typos.
Click to expand...
Click to collapse
fwayfarer said:
do we know what the offending radio versions are, and what are known good versions?
Click to expand...
Click to collapse
Currently more investigation is underway, but there does not seem to be a 100% link between radio and correct functionality.
mburris said:
From the author of the fix. See instead of just reading the first post over there, I read the entire thread (something I would recommend to anyone before posting an uninformed comment that insinuates I don't know what I'm talking about.)
On page 11 I found this:
Currently more investigation is underway, but there does not seem to be a 100% link between radio and correct functionality.
Click to expand...
Click to collapse
good work! and screw that guy, he's another one of the "know it all don't tell me anything" sperglord types this forum is polluted with. looking forward to finding a radio which works!
mburris said:
Currently more investigation is underway, but there does not seem to be a 100% link between radio and correct functionality.
Click to expand...
Click to collapse
is there a reason the stock driver can't be pulled over to cm7? copyright issues? compatibility issues?
Radio Information
I have just updated my Radio to the same that the author of this fix is using: Radio_12.35d.60.140f_26.06.03.24_M2 - TELUS WWE 1.84.661.1.
After doing so, I get the following:
After powering on:
Power status of aic3254 chip: OFF
After making a phone call:
Power status of aic3254 chip: ON
After performing voice search:
Power status of aic3254 chip: OFF
After making a second call:
Power status of aic3254 chip: ON
-and about 20 seconds later-
Power status of aic3254 chip: OFF
So, after making the first call, I use voice search once, and all subsequent calls are handled correctly.
Radio info can be found in the OP.
After installing the fix, my phone starts with the aic3254 OFF, and turns on as needed, and shuts off again.
I'm getting about a 9mA draw with this fix, so I can't complain.
skroll82 said:
After installing the fix, my phone starts with the aic3254 OFF, and turns on as needed, and shuts off again.
I'm getting about a 9mA draw with this fix, so I can't complain.
Click to expand...
Click to collapse
+1.
I'm running MIUI with a CM7 kernel and installed Build #5 of the fix and it seems to be working perfectly.
After initial boot chip is off, make a call it turns on, after call it turns back off and stays off, tested with more calls and it works perfectly.
I'm letting it idle right now so I can check my battery usage but I bet it will be nice and low now
Ok noob alert..just a prelude I've done alot of searching and reading, and *think I have some answers, but if some kind soul were to take a quick look and maybe verify what I've found, I'd be eternally grateful. I used to have a LG Optimus and easily rooted/upgraded to CM7 by reading this forum and didn't have to ask any questions.
Now I've gone and signed up for WIND (Canada) and picked up an XT720. It's my budget and I'm not overly concerned about whether or not I have ICS immediately. I'd rather have something stable and $$ saving.
OK so I'm noticing a serious difference in the way the XT720 handles the WIFI/mobile data situation compared to the LG: it doesn't. First off, there's no easy way to turn off mobile data. Secondly, enabling WIFI gets me a connection to my router, yes, but browsers and apps that require a connection just refuse to use the WIFI unless: 1. there is 3G data connection - in other words, it ain't using WIFI 2. I put the phone in Airplane Mode, and turn WIFI back on. Great, but now no phone calls or SMS. Not a viable workaround. Option 3 involves hard resetting the phone with a battery pull which sometimes works and sometimes doesn't.
From scouring around various sites, this seems to have been a common problem with 2.1 and this model of phone. And thus the workarounds I tried were also employed by others.
From what I know of all versions custom ROMs etc from 2.2 onward for other models of phones, though, this wasn't an issue, and also in 2.2 and onward you can switch off Mobile Data which will force the WIFI connection if turned on.
So is this something that I will see an improvement on if I install say CM 6.3 onward or whatever? I'll get the ability to turn off mobile data, right? And then there theoretically shouldn't be a conflict, right?
That's my biggest issue. I don't get enough 3G signal in my house to just use the mobile data connection, I absolutely have to be able to use WIFI and receive phone calls/texts at the same time, so if custom roms aren't going to help me, I'd best return the phone.
Some other things I'm curious about:
- do most of the normal functions of the phone work with CM 6.3? HD recording, camera, HDMI out etc? Anything I've missed?
- I see quite a bit of talk about people running out of RAM and using sd swapping etc is this a common problem? Even with about 20 or so apps and CM7 on my LG Optimus I was still able to maintain about 110 mb RAM free at all times by judicious use of installing apps on SD card...will I be ok?
- Probably the biggest question before I root/install...most of the guides I'm reading talk about installing various stock sbfs etc etc...I'm coming in from a WIND stock rom so I don't *THINK* I need to do this, right? I should be nandroid'ing, Open Recovery, flash custom rom....right?
Here's my specs
Xt720 Wind Canada
s/w STR_U2_05.1F.2
f/w 2.1-update1
f/w config GAS_NA_NAWIND_P012
Baseband 3GSMEPU91A_U_91.075EI
kernel 2.6.29-omap1
I realize that some of this is covered in other threads. To be honest tho some respondents/contributors aren't English first language and I just want to make sure I haven't misunderstood anything. Anyone who has done similar to what I'm trying to do, especially coming from a WIND perspective, lemme know your thoughts, please and thanks alot!
acrobat69 said:
Now I've gone and signed up for WIND (Canada) and picked up an XT720. It's my budget and I'm not overly concerned about whether or not I have ICS immediately. I'd rather have something stable and $$ saving.
Click to expand...
Click to collapse
I've picked up the XT720 myself from Wind a few days ago at the clearance price ($150 outright, no plan). They even told me there are no guarantees with the phone with its stock ROM and seemed glad to hear that I was gonna use it with a custom ROM. I knew what I was getting into and the only reason I still bought the phone is this:
http://forum.xda-developers.com/showthread.php?t=1300246
We are extremely lucky to get Gingearbread on our phones, so don't even think of ICS at this moment. As you noticed already the stock 2.1 is useless and I flashed mine the 1st day.
acrobat69 said:
That's my biggest issue. I don't get enough 3G signal in my house to just use the mobile data connection, I absolutely have to be able to use WIFI and receive phone calls/texts at the same time, so if custom roms aren't going to help me, I'd best return the phone.
Click to expand...
Click to collapse
The ROM I linked above (the only 2.3, actually CM 7.1 available for XT720) works as you'd expect with wifi and 3g, that is it uses wifi when connected to both. Any decent ROM will do that.
acrobat69 said:
- do most of the normal functions of the phone work with CM 6.3? HD recording, camera, HDMI out etc? Anything I've missed?
Click to expand...
Click to collapse
HD recording - not yet (you don't lose much anyway, the camcorder quality would be crappy, check reviews with the stock OS)
camera - yes (pretty good quality)
HDMI - not yet (I'm guessing it will be fixed very soon, the devs are working on exactly this)
everything else - yes
acrobat69 said:
- I see quite a bit of talk about people running out of RAM and using sd swapping etc is this a common problem? Even with about 20 or so apps and CM7 on my LG Optimus I was still able to maintain about 110 mb RAM free at all times by judicious use of installing apps on SD card...will I be ok?
Click to expand...
Click to collapse
This one is tricky, the phone only has about 225mb usable RAM, there's not much multi-tasking you can do with that amount but it's workable. There are some performance tweaks you can do (overclocking, CM settings, V6 SuperCharger, etc.) to make it decent. Moving apps on sd card is a good idea in order to save storage space on the phone (another limited resource at only 174mb) but has nothing to do with RAM.
acrobat69 said:
- Probably the biggest question before I root/install...most of the guides I'm reading talk about installing various stock sbfs etc etc...I'm coming in from a WIND stock rom so I don't *THINK* I need to do this, right? I should be nandroid'ing, Open Recovery, flash custom rom....right?
Click to expand...
Click to collapse
I've been wondering the same thing, what's up with all the SBFs people are talking about left and right? The answer is don't worry about them, you don't need any SBF. They are just that, stock ROMs, all 2.1. You would only need one (the Wind version) if you wanted to take the phone back for servicing and wanted to return to the original non-rooted state. Apparently even if you take a full nandroid backup with your stock ROM now and restore it later, the phone will still be rooted and this is where a stock SBF would help. I'm not gonna bother, even if I do take it back (highly doubt it, with the custom ROM it's a very good phone for $150 outright), I'm just gonna restore my stock nandroid backup.
So what you need is:
1. root the phone (personally I used SuperOneClick, google for the latest version)
2. install OpenRecovery: http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
I can send you the file you need if you pm your email address. I HATE it when I have to register on some forum just to get 1 stupid file. And you absolutely CANNOT get that stupid file anywhere else on the face of the Earth/internet.
3. install this mod for OpenRecovery: http://forum.xda-developers.com/showthread.php?t=1242259
4. go to the ROM's thread, dl the latest build linked in the 1st post, copy the zip file to your sdcard\openrecovery\updates, reboot into recovery mode, apply update, format data&cache, reboot. Done. Enjoy!
BuddyBud said:
2. install OpenRecovery: http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
I can send you the file you need if you pm your email address. I HATE it when I have to register on some forum just to get 1 stupid file. And you absolutely CANNOT get that stupid file anywhere else on the face of the Earth/internet.
Click to expand...
Click to collapse
There's an OpenRecovery apk floating around here to install ther OR bootstrap, no need to register at ModMyMobile.
:Edit:
Woodrube has it attached to this thread. Install the apk from the sdcard, reboot, then run the apk & install OR. (Now you can switch out the OR files with Mioze's modded OR)
here you go
I knew that thread would come in handy one of these days. Plus Buddy and Acro there are other handy APKs in there too.
Mioze actually have all the necessary Open Recovery files linked in his CM6.3 topic
that's the most updated version
THANK YOU THANK YOU THANK YOU to James and everyone who has responded so far - even going so far as to direct link me to files I'll need? You guys are the best!!.
I really appreciate the encouragement. I think tonight's the night.
I'll try and log my procedures and steps and make note of anything I run into for future noobs like me I might be able to help..that's how community works, right?
Wish me luck!
Good luck
One more tip: If you find that Market keeps crashing after you flash fjfalcon's ROM, flash this updated Google Apps package - gapps-gb-20111216 (dl link here).
It worked for me. Put the zip file on the sdcard right next to the ROM file and flash it just like the ROM file.
PS: Who's James?
Ah BuddyBud sorry, there is another Canadian Wind guy named Biker Bob (real name James) who was posting about his experiences in another thread, and I mixed the two of you up..
About to try this...couple questions
Has anyone watched/used Reverend's tutorial video? Results?
I don't need to unlock the phone first, right? Please tell me no, I just got it! lol
The Revs videos are a good reference & if you are talking about a sim unlock that's not necessary.
Yes Revs videos are good to show.a visual of what you should do. Don't worry about it. I know it is scary the first time but once you do it, it will become second nature. Don't forget to wipe cache, dalvik and factory reset. If you bootloop, that is probably why.
No you don't need to be unlocked. That just deals with carriers and not ROMs.
Im on the edge of the decision precipice..am not too nervous about doing this, as in fact I'm pretty technically proficient..it just seemed that this process was a bit more convoluted than the one I picked up on easily for the LG.
Decisions decisions...6.3 or go all the way to 7.1
I think I need stability...and I'm not sure I want to get into a whole bunch of swapping locations etc. I noticed The Reverend mentioned he didn't bother with swaps. Mind you, I don't even think he made an ext partition either, which boggles my mind, I was almost sure you had to make at least one for any custom ROM. I might be showing just how little I know here! lol
Is it just that 7.1 is more of an ongoing thing, or by now are most of the +/- s of both pretty much on par? I know, I should be reading all 78 pages of the damn thread, right??
Oh boy, I just read through the Bravo thread...and the LED notification sounds SOOO tempting. No LED notification bugged the hell outta me on the LG. Hmmmm...
Ok...have settled on the ROM in this thread (Bravo):
http://forum.xda-developers.com/showthread.php?t=1332410
I just want to make sure of one thing...the VERY helpful steps that you all have outlined ie BuddyBuds...they stay the same up to step 4 (ROM + update) no matter what ROM I choose, pretty much.
Brians instructions are just a slight bit confusing in that Im not sure if I have to apply just the most recent update for LED ie v1.6...or if I have to install ALL the updates from the start on up (I think there are 4 of them). To me it would seem logical that each new version would be cumulative ie include the stuff from previous versions...but I just want to make sure!
One more thing..I didnt notice any mention of gapps in the download in that thread (nor did I see a gapps apk in the files I unzipped, but might have missed it..)...if not, Ill need to apply that too, right..any special version to useÉ
Ok so...
I went with Brian's BRAVO. I followed some of the steps provided in this thread, coupled with Reverand's video. I used his OpenRecovery install method (ie original from the Dexter build, copy new over top that) because I've never installed OpenRecovery before and it just seemed confusing on other threads.
To root, I used UltimateAndroot, in order to have the ability to unroot the machine (you'll see why...)
The first thing I checked, of course, was the pull down power/status bar to see about turning off various connections (ie Wifi, Bluetooth, Refresh, Mobile Data, etc). Unlike other 2.2 Froyo's I've used, specifically..LG..there is no pull down/status bar. Damn. Went thru every Setting imaginable, but won't work. This isn't looking great.
Next thing I tested was my 3G/Wifi issue. To my dismay...the issue remains. Browser and apps are still trying to use 3G first and foremost, as far as I can see. How do I know? Because if I leave Data Network Settting to "Allowed", browser/apps work, and *seem to be using the WiFi, but the second the 3G signal fades or is dropped, I get connection issues, and WiFi is still on. If I turn Data Network Setting to "Not Allowed", it might/might not use the WiFi for a bit and then pretty consistently stop. When I mean "stop", I mean the phone is still showing connected to WiFi yet there are data connection errors on all browsers/apps that need data etc. Sometimes, if the 3G signal returns, I get the pop-up asking me to Allow the data, and if I say yes it works for a bit (but then, because of the 3G signal issue, it cuts out again).
The fix - again - turn on Airplane mode, which disconnects all connections, turn on WiFi, then go back into Call Settings and search for the Home Network again. This is crazy, I can't do this every time, and eventually it craps out again and I have to do it all over.
The other really frustrating thing is I powered it down to do a full recharge overnight...when I booted back up it didn't find my Home Network at all and I had to rescan for it. Testing that out, sure enough, rebooting the phone I have to reselect the Network. Argh.
Any thoughts? The whole necessity of being able to turn 3G data off is so I can avoid this very problem. Basically, I walk in my front door, turn off data over the mobile network, and let my WiFi do it all while I'm home. I wish I could do this as effectively as with my LG on 2.2 (and later, CM7)
acrobat69 said:
Ok...have settled on the ROM in this thread (Bravo):
http://forum.xda-developers.com/showthread.php?t=1332410
I just want to make sure of one thing...the VERY helpful steps that you all have outlined ie BuddyBuds...they stay the same up to step 4 (ROM + update) no matter what ROM I choose, pretty much.
Click to expand...
Click to collapse
Once you get to step 4 inn Buddy's list check out this. It will explain it a little bit better. Brought someone back from the brink on this thread. Where is says Dexter, just replace that with Bravo.
Brians instructions are just a slight bit confusing in that Im not sure if I have to apply just the most recent update for LED ie v1.6...or if I have to install ALL the updates from the start on up (I think there are 4 of them). To me it would seem logical that each new version would be cumulative ie include the stuff from previous versions...but I just want to make sure!
Click to expand...
Click to collapse
Per Brian's OP the v1.9 has all the patches.
v1.9,A new Nandroid IMG backup,All patches included(20111217).
Click to expand...
Click to collapse
One more thing..I didnt notice any mention of gapps in the download in that thread (nor did I see a gapps apk in the files I unzipped, but might have missed it..)...if not, Ill need to apply that too, right..any special version to useÉ
Click to expand...
Click to collapse
Gapps is for CM builds. Bravo is a 2.2 build.
Side note: If you are going to partition it is up to you. I and a few other don't but it is really a personal preference. When I did, I used MiniTool Partition Wizard and it worked like a charm.
A few things though:
1: Your partitions must be set up this way---> Fat then EXT2/3 then Swap (if you choose-I don't and never did-requires you to fastboot a custom kernel and since this is your first experience, I would not suggest it)
2: Sizes. Many noobs will set their EXT2/3 partition to 1gb. That is way too big and you are just wasting space. I find that somewhere between 350-400mb is more than enough.
3: Do not convert your Ext partition to EXT4 unless the ROM you choose supports it. If/when the time comes, use MZ's open recovery utility to do it and not GPArted or MiniTool. The creat a Hugefile that has to be deleted and is a PITA.
4: If you do decide to partition, you will have to boot up fully, then go into your root explorer and in the SD-ext, you will need to create a folder called App (not apps-no S) so it will look like this sdcard/sdext/app. Then reboot and your apps will auto-install there.
Sorry for the long post and good luck.
---------- Post added at 11:30 AM ---------- Previous post was at 10:42 AM ----------
acrobat69 said:
Any thoughts? The whole necessity of being able to turn 3G data off is so I can avoid this very problem. Basically, I walk in my front door, turn off data over the mobile network, and let my WiFi do it all while I'm home. I wish I could do this as effectively as with my LG on 2.2 (and later, CM7)
Click to expand...
Click to collapse
Once you click on WIFI it should take over as your primary source of data. Not sure why unless I think I might have figured it out. Go into settings>wireless>tick your WIFI and once your router pops up leave it alone and hit your menu button. Set your WIFI sleep policy to NEVER and I bet that takes care of it. Pretty sure that is toggling off your WIFI when 3g is present.
Other solution is Widgetsoid and Elixir both have a widget to toggle off data (so does Beautiful widgets too for that matter). You can use those but I really think the above solution should work for you.
Woodrube said:
Per Brian's OP the v1.9 has all the patches.
Click to expand...
Click to collapse
Ah, figured..however when I go into LED Notification, it says "revision 1.6" (or some wording to that effect) at the bottom. Maybe that's just an error, but I just used that to gauge whether or not I had installed the latest revisions etc.
LED Notification works for text messages. I haven't seen it work for calls yet, but maybe I'm doing something wrong. I call the phone, the screen lights up that there's a call, and then ultimately closes when noone answers it. It was at this point that I'd assume the LED notification would come on. Screen is out, so LED, right?
Woodrube said:
Gapps is for CM builds. Bravo is a 2.2 build.
Click to expand...
Click to collapse
Ok I guess I goofed then, because I tried to update with Gapps after I installed Bravo. One thing I noticed is that I wasn't prompted to sign up/into my Google accounts or set up the phone when I rebooted following the Bravo ROM + Gapps install..that had always happened on my LG when I did CM installs...your explanation makes sense!
But...isn't CM6 basically 2.2 and Bravo basically 2.2? Or maybe I misread that.
At any rate, the real reason I updated Gapps is because I wanted the "new" Market look. I don't like the old one very much, really like the My Apps function. Is there way I can just patch this in to Bravo?
Woodrube said:
Side note: If you are going to partition it is up to you. I and a few other don't but it is really a personal preference.
Click to expand...
Click to collapse
Why do people partition? I did it on my LG, but never used it. Partitioning has nothing to do with installing user apps to the SD card, right? I can do that anyways, true?
Speaking of which..in CM there is the ability to set the default install location. I searched to find something similar in Bravo, to no avail. Is there a way to do this?
Wait...I think you just gave me the answer to both these questions...duh me..
Woodrube said:
4: If you do decide to partition, you will have to boot up fully, then go into your root explorer and in the SD-ext, you will need to create a folder called App (not apps-no S) so it will look like this sdcard/sdext/app. Then reboot and your apps will auto-install there.
Click to expand...
Click to collapse
I guess I do in fact want to partition, then. I can't imagine how one wouldn't want to, I mean you don't want apps clogging up internal memory, right?
Woodrube said:
Sorry for the long post and good luck.
Click to expand...
Click to collapse
Never apologize for long posts...I'm the worst at it and I love pouring over every single last detail. I'm sure there are lurkers who appreciate also, I know I really did when learning on my LG. Thanks a million!!
Woodrube said:
Once you click on WIFI it should take over as your primary source of data. Not sure why unless I think I might have figured it out. Go into settings>wireless>tick your WIFI and once your router pops up leave it alone and hit your menu button. Set your WIFI sleep policy to NEVER and I bet that takes care of it. Pretty sure that is toggling off your WIFI when 3g is present.
Other solution is Widgetsoid and Elixir both have a widget to toggle off data (so does Beautiful widgets too for that matter). You can use those but I really think the above solution should work for you.
Click to expand...
Click to collapse
DOHHHHH!!!! I knew I had forgotten something about past settings that made my LG work so well.. I have modified the Wi-Fi sleep policy and hopefully it will work better now! One constant in all the issues I was having, now that you've mentioned this, is that the screen was sleeping/timing out while things were going on. I'd bring it back up, and be all "like, wtf" when my browser wouldn't work or apps that were downloading hung, etc. Mind you, it probably should have reconnected by itself, but whatever, if it doesn't, there's no harm in using Never Sleep for WiFi. I'm not that much of a stickler for battery usage. I go to bed, I charge the phone, I wake up, repeat. I don't need 4 days battery life and if I ever am in a situation where I do, I'm camping or somewhere remote ie no WiFi hence this doesn't apply as I'd just toggle WiFi off completely anyways.
You're right, I could use a Widget to manage my connections and I managed to grab Beautiful when it was 10 cents..but those reside on the screen and I would love to get that pull-down bar back, just so handy to drag down no matter what app/screen you're in...I know, I'm picky
You know what? I got a Notification Toggle app on my PC at home that I'll upload here tonight. I just remembered it while I was at lunch. It is from an older ROM so not sure it will work but worth a try. Usual directions. Push it to /system/apps reboot. It should be just what you are looking for if it works. Might not though so you'll just have to see.
CM6 is 2.2 and so is Bravo only Bravo was made from the official Korean update that was handed down and Mioze has created the CM6 from source. So yes they are both 2.2 but very different.
Edit: I have the latest Market.apk too. It is floating around here somewhere but I can't find in for some reason. I'll upload them tonight.
acrobat69 said:
Decisions decisions...6.3 or go all the way to 7.1
Click to expand...
Click to collapse
try them both first, then see which one you want to use as your daily driver.
i personally like the 6.3 better because it runs the fastest even on stock speed 720 Mhz
you can use Open Recovery to do a full backup, and switch back and forth between 7.1 and 6.3 until you decide which one you like best
7.1 has more themes to choose from and is more up to date, but... less free resources vs. 6.3 which is indirectly related to why it feels less quick than 6.3
7.1 feels similar to the speed you get on the stock ROM from Wind, 6.3 feels like a brand new device
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !
Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?
crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.