yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] PsychoPhreak:
So I'd say this ROM is damn near perfect at this point Emmanuel and everyone involved, except for one little weird issue that I've had. It seems to be a graphical/overlay issue, and I wonder if it falls under the same line as to why the electron crt screen off had to be edited to a fade out (not that I mind the fade out, it works, but the crt was pretty cool looking, and it's the only other thing I could imagine being related.) I'm not deep enough into this stuff to know what caused that and what the workaround/fix was but the weird issue I'm having on here is with a silly zynga game, Words with Friends.

99% of the app works without issue, but often when I load a new game, all my letter tiles will be missing (just not drawn on screen). If I go into the chat window and back to the board, they'll be back. Sometimes if I try to shuffle the tiles they'll freeze in place during animation, and I'll have to do the chat/return again. Sometimes I'll try to zoom the board and it'll stick, chat/return always seems to fix. The worst is sometimes the board will flicker between black/blank and it being there. It's not that crazy an app and I can't imagine what's freezing up during animation/draw in there when everything else on this ROM seems perfect and smooth, just thought I'd report it though. Not sure it's even fixable, but if it got addressed, this would def become my new DD!

I'm only mentioning because bugs are asked to be reported, but amazing amazing work between this and everyone else dev's, please let me know if I can provide any additional info/details that might assist with troubleshooting this.
[T-Mobile myTouch 4G Slide] acwest:
hang/reboots

As I mentioned before, I ran into problems with my device hanging/rebooting, often within seconds after turning it on. On my initial installation it was working fine, and call quality was good, but after I got about half way through a Titanium Back Up restore, it hung, and I haven't gotten more than thirty seconds of up-time since. The odd part is that even after wiping /data, /cache, /system, and dalvik cache, and reinstalling, it is still in this state. It is like something on the device was changed during that app restore, and I can't figure out how to reverse it.

If I restore a backup from my latest 4.2, everything is fine, so whatever it is, it is 4.3 specific.

Does anybody have any recommendations on what I can try to get the 4.3 to boot and stay booted? Is there anything else I can wipe? I am about to try installing without gapps, but don't really expect it to make much difference...

Edit:

Well, I seem to have narrowed the problem down somewhat. It appears that there is something on my sd card that 4.3 doesn't like now. I pulled it out as a test, and everything is fine again.

I am going to copy the information off of the card, re-format it, and then copy the parts of the image I actualy need back onto it. We will see how that works out. Any recommendations on the best method to use to format it?
[T-Mobile myTouch 4G Slide] SKAm69:
I think the best method to format the sdcard for using with phone is to format it using Android's built in formatting tool. Probably under 4.3 system if you say that matters.
[T-Mobile myTouch 4G Slide] Vauvenal7:
If you plan an update, could you include halo? :)

Would be awesome!

Greets Vauvenal7

Sent from my HTC MyTouch_4G_slide
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
This will work in ICS so it should work in JB too. Download Notepad++ and open up the build.prop file located in your system folder. Scroll down to the last entry before "Additional Build Properties" and make this line your NEW last entry....

qemu.hw.mainkeys=0

Then save your changes, rezip your ROM (no compression) & dirty flash right over the top of it. When you boot back up you should have a brand new Navigation Bar.
[T-Mobile myTouch 4G Slide] ibawanzingee:
Oh, that's great! Thanks so much, Weekends!
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
If there was a "You're Welcome" button I would surely hit it for you right now. LMAO
[T-Mobile myTouch 4G Slide] Paitor:
Did it fix the problem? I will try it too if it works.
[T-Mobile myTouch 4G Slide] acwest:
Well, it worked, in that my phone stopped rebooting almost instantly. I still had a problem after I installed gapps core version, it hung after signng up to my google account. After the reboot, it seems okay, though.

Incidentally, I now have the /proc/last_kmsg contents from when it hung, the msm watchdog suspended the phone and did a full dump, which might be useful. At the point where the watchdog process kills it, the only thing unusual in the log is a lack of stuff in the log. If it happens again, I will grab any more kernel logs.

If it means anything to anybody, the crash was in mmcqd, it looks like...

EDIT: Seeing as it is mmcqd that is crashing, I suspect the reformatting my SD card did not solve all of my problems, I should get another one...

[ 238.366577] PID: 118, Name: mmcqd/0

[ 238.367218] Function entered at [<c010c9b8>] from [<c010a180>]

[ 238.367858] Function entered at [<c010a180>] from [<c0167b54>]

[ 238.368225] Function entered at [<c0167b54>] from [<c01ea434>]

[ 238.368865] Function entered at [<c01ea434>] from [<c01ed7ac>]

[ 238.369201] Function entered at [<c01ed7ac>] from [<c01e9bc4>]

[ 238.369842] Function entered at [<c01e9bc4>] from [<c0100050>]

[ 238.370208] Function entered at [<c0100050>] from [<c010664c>]

[ 238.370819] Exception stack(0xce4a3e18 to 0xce4a3e60)

[ 238.371154] 3e00: 00000002 00000002

[ 238.371826] 3e20: 00000008 00000001 ce4a3e6c ce4a2000 00000001 c14fe320 c14fe320 014bd000

[ 238.372497] 3e40: 00000001 c14fe328 00000002 ce4a3e60 c01120b8 c01d38f8 20000013 ffffffff

[ 238.372863] Function entered at [<c010664c>] from [<c01d38f8>]

[ 238.373504] Function entered at [<c01d38f8>] from [<c01d3cec>]

[ 238.373840] Function entered at [<c01d3cec>] from [<c05b9d3c>]

[ 238.374481] Function entered at [<c05b9d3c>] from [<c01c3600>]

[ 238.374847] Function entered at [<c01c3600>] from [<c05ce0dc>]

[ 238.375488] Function entered at [<c05ce0dc>] from [<c05bccf0>]

[ 238.375823] Function entered at [<c05bccf0>] from [<c05ca0d4>]

[ 238.376464] Function entered at [<c05ca0d4>] from [<c05cbeb4>]

[ 238.376831] Function entered at [<c05cbeb4>] from [<c01bc910>]

[ 238.377441] Function entered at [<c01bc910>] from [<c0107610>]

[ 238.377807]

[
[T-Mobile myTouch 4G Slide] Paitor:
Ok, thanx. Then I think I will stuck to my solution with an older kernel
[T-Mobile myTouch 4G Slide] acwest:
Actually, things are working pretty well now, and I seem to have a suspicion of what is wrong. As soon as I installed Maps, it started hanging again, always in mmcqd/0

So I took a look on the SD card, and maps appeared to be installed onto the sd card, which was causing issues. For now, I am skipping Maps. I will pick up a newer, faster SD card on the weekend, in the hopes that it will fix it. Possibly going with something besides the standard fat32 will also help, I seem to recall something about that, once upon a time
[T-Mobile myTouch 4G Slide] Darnell_Chat_TN:
I just upgraded my wife's "Slide" from MikTouch-0.5 to this ROM. This is amazing. Now she's got the same level of Android on her Slide as I have on my HTC One :D .

The Slide is the last of the good Android devices with a keyboard. This ROM has given it new life.

I have the version of Maps that is in the OP loaded on the Slide. But now Google Play wants to update Maps. Does anyone know a way to have Google Play stop nagging about it? And I'd like to be able to use the "Update All" button without maps being updated. I guess I could freeze maps when running updates, and turn off update notifications? Or does anyone know a better way?

Great ROM Emmanuel U! :good:
[T-Mobile myTouch 4G Slide] demkantor:
I believe the option in titanium backup to brake market link should work fine, personally I just hit update all than click on any app I don't want to update and stop it... But im strange
[T-Mobile myTouch 4G Slide] acwest:
I ran into the same problem again, wish I knew what triggered it exactly. It always seems to be MMC issues, though. Doing some research, I have found a couple of kernel patches for the MMC code that may help, but they seem to be from 3.4 or so, I will have to actually do some work to determine if the patches I found have any bearing on the MMC code we are actually using...
[T-Mobile myTouch 4G Slide] acwest:
Kernel differences

Are there any differences between the kernel in this ROM and the WildKernel Reloaded v007? Even after getting a new Kingston 32GB microSD card, I am still getting issues, all it tends to take is installing gapps core.

The exception is always in mmcqd/0, and I suspect a kernel bug. The main thing that has me confused is that running SilverL's 10.1 with the WildKernel Reloaded 007, I have no issues whatever, and from what I can tell, the kernel's should be very close or identical to each other... I did try to install the WK007 over top of this kernel, but then it alwas got stuck running apps, so it won't boot. It was worth a shot :)

Any recommendations on debugging the MMC issue? IS there an easy way to convert my stack dump to something with useful function names?
[T-Mobile myTouch 4G Slide] Darnell_Chat_TN:
I'll use the same method as you, update all and STOP the Maps update when it begins.

The Titanium backup method only works temporarily. The Dev says Google has made it too hard to make the detachment from market (Google Play) permanent.
[T-Mobile myTouch 4G Slide] killkillkill:
Take the update, then find the apk file, rename it to "Maps.apk", copy it into your /system/app/ directory. When you copy it into /system/app, it should automatically delete the user installed file wherever it was.

Also, no, it was NOT the last good android keyboard phone. Photon Q was one, better resolution, but unfortunately, no AWS band. Samsung Relay, same resolution, way better SoC (S4-Krait vs S3-Scorpion), more RAM, and unbelievably better battery life.
[T-Mobile myTouch 4G Slide] SKAm69:
Maybe but you're forgetting the camera wich is important for many people including myself. And the cameras on those two are bad comparing to mt4gs
[T-Mobile myTouch 4G Slide] killkillkill:
There is more to a good camera than the number of pixels. We have both a relay and a doubleshot, and the cameras both suck equally.
[T-Mobile myTouch 4G Slide] david31262:
Instability Problems -> Min CPU Frequency ?

Note, I haven't tried this ROM yet. I'm currently running SilverL's 4.2.2..

For those of you having instability problems, can you take a look at the Min CPU Frequency. My phone doesn't seem to like 96 Mhz (spontaneously rebooted 3 times in 1 hour while listening to an audiobook). Changing the setting to 128 seems to solve the problem.
[T-Mobile myTouch 4G Slide] Ziida:
This is horribly off topic to the thread and we should maybe start a general discussion topic about it... but how is development for the Relay? are there nice modern (jellybean ideally) stable ROMs?
[T-Mobile myTouch 4G Slide] orangekid:
So you follow up a statement about people getting off topic with asking about ROMs for a different phone? :confused:

OP doesn't seem concerned with a little bit of off topic so I think we're fine here, so long as it doesn't go overboard...

Even so, let's try to keep this more oriented to the ROM at hand.
[T-Mobile myTouch 4G Slide] Ziida:
Haha yep I did. I just quickly wrote that out on mobile and hoped someone else would start the thread if they were interested :silly:
[T-Mobile myTouch 4G Slide] Paitor:
Strange, I'm running WK007 that I installed after I installed JellyBean Ds v1.5. Have worked like a charm for almost three weeks.
[T-Mobile myTouch 4G Slide] killkillkill:
Does this answer your question? http://get.cm/?device=apexqtmo

;)

If you're interested in it, might head over to the Relay section to continue; http://xdaforums.com/forumdisplay.php?f=2182
[T-Mobile myTouch 4G Slide] acwest:
I seem to have a unique phone, I hate it when that happens :)

What really bothers me about it is that it works just fine with 4.2 JellyBean, I can understand my phone being broken, it just seems weird that it could be broken in a way that is only noticeable in 4.3.

I tried increasing the minimum CPU speed, but it didn't help... I am hoping we get a new kernel soon, it may help...
[T-Mobile myTouch 4G Slide] killkillkill:
Ok, on the development/maintenance of this system image;

First off a note; OP's manifest is... questionable. I'm not going to say that its bad, but it is extremely large and brings in a lot of changes that in a lot of cases, do nothing, in other cases, could potentially cause defects that wouldn't be present in other devices, particularly, running a more vanilla CM.

I've forked repos and simplified dramatically;

Nobody here is deserving of any assistance, so screw you all, suffer with the garbage that you're being fed.

Now AOSP/CM is actually quite easy to build, the main stumbling block most people will come into is just in getting the dependencies installed on their favorite flavor of Linux distribution.

But the build itself is very easy;

obtaining the "repo" command, step 1-2 from http://source.android.com/source/downloading.html

initializing a build root "mkdir someplaceforcmbuild; cd someplaceforcmbuild; repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2"

installing your local manifest by copying above code block into "somplaceforcmbuild/.repo/local_manifests/local.xml"

sync the repo "repo sync"

do the build ". build/envsetup.sh; brunch doubleshot"
[T-Mobile myTouch 4G Slide] Emmanuel U:
Yes however a complete vanilla build of CM will bring some bugs specific to our device, that's why we need so of their repos changed to fit us such (along with my personal changes that I feel make it better)
[T-Mobile myTouch 4G Slide] Emmanuel U:
Uploading right now
[T-Mobile myTouch 4G Slide] Emmanuel U:
Updated to 1.6 LTS until JellyKang is brought back to speed, enjoy :)
[T-Mobile myTouch 4G Slide] Vauvenal7:
To keep on topic

I guess, now that the ROM got rebased i cant dirty flash it over 1.5?

Greets Vauvenal7
[T-Mobile myTouch 4G Slide] Emmanuel U:
It's a minor rebase you'll be fine. I will usually mention if a full wipe is required prior to an upgrade

First off...where do you see any wimax commits? Why would I even mess with wimax when our device doesn't support it. Second, all my repositories are mean't to work with all devices under our same arch....not just the doubleshot. So seeing 3D camera commits were most likely meant for the Evo 3D but were automatically merged in from other repos....this merge would not apply seeing as the camera won't compile these changes unless told so in the configuration (which it is not). Third, latinime was just reset to a point in which it didn't produce graphical errors...there may have been a commit upstream that fixed but I'm not monitoring it as that is not my priority. I add in the htc common configuration because I also build recovery images with my roms for personal use. Last but not least, a seperate toolchain is used for this device as it seems despite CM's commits "fixing" the problem, compiling servicemanager with google's latest toolchain corrupts the executable and segfaults on startup. I simply changed the default select of a menu item since the option doesn't not work well on our device and may mimick battery drain (there is no way to have done this through the overlay else I would've....why would I purposely host my own repo if a simple overlay could've been made?). If your build is so much better than mine, why not release it instead of just bragging about how much it is supposedly better? I'm open to criticism or else I wouldn't ask about what's wrong with my rom...however I don't need to be insulted. I don't see why something like that would need to be stated and not known through common knowledge. Also if everyone on this forum was capable of producing a rom, then there would be no need for this site. It does not make an individual lazy because they choose not to replicate someones work.
[T-Mobile myTouch 4G Slide] acwest:
Trials and Tribulations

My problems continue, even with the new version, unfortunately. It seems certain that it is something unique to my device that is triggering the crashes, as it appears that nobody else has been able to reproduce the issue. My latest attempts have been focused on reducing possible differences between my device and everybody else's. The first thing I tried was replacing my battery, as the one I was using was a cheap knock-off that came with the phone, and I am fairly sure it was causing issues with my camera flash earlier (not to mention new toys are good...). For now I have a new Evo battery in the phone, which seems to be working fine, but has not resolved the issues. Next attempt was to try the wire trick to make my phone S-Off. There were two reasons for this, I believe most of the devs on here are already S-Off, so my phone is now more closely matched to them, and all of these attempts require a lot of flashing, and it is MUCH easier when you don't need to use fastboot to flash the kernel.

The good news is, I have attained the coveted S-Off state. The bad news is it didn't help. It was more annoying than expected to get the wire trick software working while using a Mac. It turns out that VirtualBox USB 2.0 emulation is not reliable with the ControlBear software, once I figured that out things went much better...

As nothing else is working so far, I am probably going to have to follow the advice of our helpful friend killkillkill and build my own ROM, in an attempt to make it easier to debug the issues on my device. I have been trying to avoid that, as my day job has me quite busy enough doing app development, but I really want to get this thing working...

Unfortunately, ROM building on a Mac still seems a little flaky, I may have to work in a VM to get it all going...
[T-Mobile myTouch 4G Slide] Emmanuel U:
I may have missed, but what was the problem you were experiencing?
[T-Mobile myTouch 4G Slide] acwest:
Crashes

Generally, I have been experiencing crashes of the device shortly after booting. The crash usually takes place in mmcqd/0. I have stack traces, but there isn't much I can do with them so far. I haven't investigated the problems running the latest build all that thoroughly yet, but in the 1.5 build, once it starts crashing, it will generally crash within a minute of booting the device. I have had it work up to a day before this point, however. The problems seem to be related to Google Play, as it usually happens when I install something such as YouTube. One of the weird things about it is that I can have a perfectly working system, do a backup, then install YouTube, and it will immediately start crashing the device. At this point uninstalling the troublesome app, or even restoring the back-up is not sufficient to fix the problem. Restoring my SilverL 4.2 build does fix it, however. It's driving me nuts...
[T-Mobile myTouch 4G Slide] Emmanuel U:
Is your problem specific to this rom or in general? (I'm trying to narrow down the source of the error)
[T-Mobile myTouch 4G Slide] abe5:
Dirty-flashed v1.6 over v1.5 aaaaaaaand we're good. No issues. Thank you! :)
[T-Mobile myTouch 4G Slide] acwest:
So far, just this ROM, but I haven't tried any other 4.3 ROMs yet... I have been using WildKernel Reloaded 007 on my 4.2, and it works fine...
[T-Mobile myTouch 4G Slide] PsychoPhreak:
Was hoping they were gone, but the damn graphical issues with Words with Friends still persist. Relatively minor bug, but enough for me to have to pass as a DD for now. So stupid and weird, but great overall still of course!
[T-Mobile myTouch 4G Slide] acwest:
As an additional note, I am now using WildKernel Reloaded 008 without difficulties with 4.2.2. v1.6 seems to be worse than 1.5 on my device, in that it crashes much earlier. I am beginning to suspect my battery as being part of the problem, as I am getting invalid batteryId messages, and a message:

[BATT][tps65200] TPS65200 shutdown

Although that appears to be related to my camera flash problem, not the 4.3 problem. I don't tend to believe in coincidences much, however, so it is certainly possible they are related... If I can find a totally stock battery, I am going to try everything with it and see what it fixes...
[T-Mobile myTouch 4G Slide] Pons:
Thread closed for some cleaning....

Edit: And reopened. @ all, please remember this is a development thread, for a specific ROM, so try to keep on topic. On that note, constructive criticism is good, as long as it's done...tactfully. If someone is being difficult, don't reply and stoke the flames, use the Report Post system. That's what it's there for.
[T-Mobile myTouch 4G Slide] Paitor:
If you missed it Emmanuel U I also had the issue with 1.5. I fixed it with an older kernel. See this post below. Dosen't seem to work for acwest though.

[MENTION=3077179]acwest[/MENTION]: The camera flash issue is battery related. I have it with my anker 1900mah battery. My own guess is that the voltage is much lower on these batteries. When the autofocus and flash is combined it takes alot of power. Low voltage leads to higer current. Some kind of short circuit protection is triggered in the battery and it cuts power = phone dies. Anyway, flash works fine with my "golden" battery. But that gives me very bad battery life. 2450mah is just fantasy figures after measuring it it is even 100mah lower than the anker.
[T-Mobile myTouch 4G Slide] Saem persun:
Nice and smooth rom, thanks! I don't see the torch shortcut in the tiles anymore after the latest update. And there's no torch option for button shortcuts for the lock screen. It was extremely useful to have the torch via hardware button. Could you please get them back?
[T-Mobile myTouch 4G Slide] Emmanuel U:
Oops I know what I did, I'll have an update hopefully today fixing that
[T-Mobile myTouch 4G Slide] Paitor:
Same Issue with v1.6. After full whipe and installation the phone hangs on cyanogenmod config screen or sometimes already on the boot circle. This time I got an error when trying to install wildkernel 007 on top of it.
[T-Mobile myTouch 4G Slide] acwest:
I had the same issue you did. I am currently working on editing the 007 installer script to allow version 4.3.1 as well as version 4.3. My first attempt didn't work, so I am trying again today. I wasn't able to make it work with 1.5 because my device was S-On, so while I could flash the boot.img, I was probably getting mismatched kernel modules. After some effort, I got the wire trick to work and am now S-Off, so I am hopeful that 007 may fix my issues. If it does (and as it fixes yours, I am somewhat optimistic on this) then we just need to investigate whatever differences there are between the kernel in 007 and 1.5. It doesn't appear as there should be much difference at all, though.
[T-Mobile myTouch 4G Slide] Paitor:
Great, seems like [MENTION=4193353]Emmanuel U[/MENTION] is a busy man these days so it's good that someone else is looking at this issue.
[T-Mobile myTouch 4G Slide] acwest:
I've been meaning to devote more time to this, but due to work, I develop on a Macbook Pro, which seems to have a few issues with building ROM's. I have seen a few threads devoted to getting that working, but haven't had time to really look at it. I am quite jealous of all of these people who have 4.3 goodness, though :)
[T-Mobile myTouch 4G Slide] Emmanuel U:
If you download the latest WildKernel (008), it supports all the latest versions of android
[Nexus 4 Q&A, Help & Troubleshooting] Kyle C:
I was wondering if its possible for devs to mod the Hangouts app? If possible, I'd like to be able to have a quick reply function within the notification area similar to quick reply mods with the MMS app that you can have with CM or AOKP ROMS.
[General Questions and Answers] phositadc:
If you have an unlimited data plan on Verizon, can you switch back and forth between an iPhone and an Android phone?

Or do iPhone and Android have different data plans?
[General Questions and Answers] papafizzle:
Thanks

Thanks for the post