yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] anitgandhi:
I only got to use it for a bit but here is what I noticed

It was heating up like crazy, 64 Celsius for CPU

2nd wasn't being disabled as needed, mp decision sort of issue

Camera was all like white washed out, like it was on high exposure settings.

General cm 10.2 thing, why keep camera and focal?

Haptic feedback on the keyboard has become a lot more subtle. I like it!
[T-Mobile myTouch 4G Slide] Emmanuel U:
Did you try the regular camera app? Focal is really buggy for our phone
[T-Mobile myTouch 4G Slide] bit1:
Mic seems to work fine now. Used Now and made a call successfully. Camera app works as does front facing as long as you don't open focal. It does not seem that video recording is working at this time. If focal freezes it becomes can't connect to camera even on instagram. Also the phone does feel like it's running hot
[T-Mobile myTouch 4G Slide] anitgandhi:
yeah same thing happened on regular camera app, it was either really washed out (the preview and the actual image) or really dark.

btw those things i listed were on version 1.0
[T-Mobile myTouch 4G Slide] Saem persun:
What about the maps v7? Is there any flickering?
[T-Mobile myTouch 4G Slide] Emmanuel U:
1.7 is currently being uploaded to my Copy Hosting (link in sig), however I will not officially release until one of my main hostings are back online (Goo or TRU).

Btw 1.7 has the recent flash issue fixed.
[T-Mobile myTouch 4G Slide] Paitor:
Dosen't help if that is the kernel that makes our phones to freeze and reboot. Please take a look at the issue above. I will gladly try to help with all input that you need to solve this issue. The issue is pretty clear, Istall JellyBean v1.5 the issue is present. Install wildkernel 007 on top. The issue is gone.
[T-Mobile myTouch 4G Slide] acwest:
So far I can verify that 1.5 with 007 on top seems to be working for me too. There seems to be some change between the 1.5 kernel and the 007 kernel (hard to say what, they appear to have been produced at about the same time, but I can look to see if there is anything) This doesn't really explain why my phone works with 4.2.2 (or 3, I can't remember) with 008 on top, though. Could be a kernel issue which is only exposed by a userspace change between 4.2 and 4.3...

I am currently re-loading my apps, we will see if things continue working, as in my previous attempts, it often worked for a day or so until suddenly not working anymore...
[T-Mobile myTouch 4G Slide] acwest:
I have now re-installed all of my apps, and am still running successfully, with 1.5 and 007 kernel. I suppose the next thing to do is to flash the 008 kernel and see what happens...

---------- Post added at 04:03 PM ---------- Previous post was at 03:48 PM ----------

And back to 007, 008 hung while "Running apps", the /proc/last_kmsg showed a wireless reset, but I don't know if it is related. The end of the log is:

[ 123.956909] [BATT] power_supply_changed: battery at 123880843094 (2013-10-30 19:55:09.499818982 UTC)

[ 141.626159] TSENS: Current CPU Temperature is: 55

[ 155.452301] ## wifi_probe

[ 155.452331] wifi_set_power = 1

[ 155.452331] doubleshot_wifi_power: 1

[ 155.573852] wifi_set_carddetect = 1

[ 155.573852] doubleshot_wifi_set_carddetect: 1

[ 155.573852] mmc2: Slot status change detected (0 -> 1)

[ 155.574554]

[ 155.574554] Dongle Host Driver, version 5.90.125.94

[ 155.574554] Compiled in drivers/net/wireless/bcmdhd on Oct 21 2013 at 20:38:41

[ 155.621154] mmc2: queuing unknown CIS tuple 0x91 (3 bytes)

[ 155.621246] mmc2: new high speed SDIO card at address 0001

[ 155.622528] F1 signature read @0x18000000=0x9934329

[ 155.624755] DHD: dongle ram size is set to 294912(orig 294912)

[ 155.625518] wl_create_event_handler thr:2dc started

[ 155.625915] dhd_attach thr:2dd started

[ 155.626007] dhd_attach thr:2de started

[ 155.626098] dhd_attach thr:2df started

[ 155.626281] wifi_get_mac_addr

[ 155.626281] doubleshot_wifi_get_mac_addr = d4 20 6d 25 c2 2a

[ 155.626922] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33

[ 155.627563] wifi_set_power = 0

[ 155.627563] doubleshot_wifi_power: 0

[ 155.736938] acc_open

[ 155.737030] acc_release

[ 155.771331] =========== WLAN placed in RESET ========

[ 155.941009]

[ 155.941040] Dongle Host Driver, version 5.90.125.94

[ 155.941040] Compiled in drivers/net/wireless/bcmdhd on Oct 21 2013 at 20:38:41

[ 155.941040] wl_android_wifi_on in

[ 155.941040] wifi_set_power = 1

[ 155.941040] doubleshot_wifi_power: 1

[ 156.062225] =========== WLAN going back to live ========

[ 156.062225] sdio_reset_comm():

[ 156.129577] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.

[ 156.212249] doubleshot_wifi_get_mac_addr = d4 20 6d 25 c2 2a

[ 156.219482] [VIB] pm8xxx_vib_enable, er.ServerThread(parent:zygote): vibrates 0 msec

[ 156.220489] [VIB] pm8xxx_vib_enable, Thread-66(parent:zygote): vibrates 1 msec

[ 156.220489] [ATS][set_vibration][successful]

[ 156.221496] [VIB]pm8xxx_vib_timer_func

[ 156.228240] [VIB] pm8xxx_vib_enable, er.ServerThread(parent:zygote): vibrates 0 msec

[ 156.368774] CFGP2P-ERROR) wl_cfgp2p_supported : wl p2p error -23

[ 157.425659] wl_bss_connect_done succeeded status=(0x9)

[ 157.522735] wl_bss_connect_done succeeded status=(0x11)

[ 157.522827] qtaguid: iface_stat: stat_update() wlan0 not found

[ 157.963897] SELinux: initialized (dev mmcblk1p1, type vfat), uses genfs_contexts

[ 157.972290] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[T-Mobile myTouch 4G Slide] Emmanuel U:
How about running v1.7 with 007 flashed
[T-Mobile myTouch 4G Slide] Emmanuel U:
I'll look into it, but I hope it's not bugging out for the same reason that Google Maps 7 is glitching out.....because that isn't an easy road.
[T-Mobile myTouch 4G Slide] acwest:
That doesn't work because 007 won't install on 4.3.1. I thought I had it figured out to update the scripts that check the version, but I must have had a problem somewhere, as it failed with no useful message. I am going to make another attempt at making a 4.3.1 compatible version of 007, if I get time...
[T-Mobile myTouch 4G Slide] Emmanuel U:
Oh yea (my bad a bit tired, not thinking to the best of my ability), so I assume 008 gives problems on 1.7?
[T-Mobile myTouch 4G Slide] acwest:
008 does have problems on 1.5, unfortunately. Do you have commit hashes for the various kernel releases, or are they tagged somehow?

---------- Post added at 07:02 PM ---------- Previous post was at 06:21 PM ----------

I managed to fix the really stupid typo I added to the updater script, and I have now successfully installed 1.6 with WildKernel 007, and it appears to be working fine...
[T-Mobile myTouch 4G Slide] Emmanuel U:
Do you mean 1.7?
[T-Mobile myTouch 4G Slide] acwest:
I did 1.6, as 1.7 hasn't shown up on goo yet. Seeing as you mentioned it though, I found 1.7 from the links in your sig and am busily downloading it now :) I will try with it's stock kernel in case it works, and if it doesn't, I will try my hacked 007
[T-Mobile myTouch 4G Slide] acwest:
1.7

I tried 1.7 without installing the 007 kernel over it, but it still had the hanging problem. After installing 007, the phone app would crash on boot, and keep crashing. I am now back to 1.6 with 007, we will see how it goes...
[T-Mobile myTouch 4G Slide] Paitor:
Can you PM me your hacked 007 so I can try 1.6 too.
[T-Mobile myTouch 4G Slide] Paitor:
Got it. Works for me too.
[T-Mobile myTouch 4G Slide] acwest:
Have you tried it with 1.7? My issues may not be entirely the same as yours. It's nice to know that my phone isn't the ONLY one in the universe, though :)
[T-Mobile myTouch 4G Slide] Paitor:
I can try. What was the issues you got with 1.7?

Edit: Didn't work. Phone app crashes
[T-Mobile myTouch 4G Slide] acwest:
When I installed 1.7 without flashing the new kernel, I was getting the same hang issues we had with 1.5 and 1.6. With the 007 kernel, I get continuous crashes of the phone app.

---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------

I am running 1.6 so far, and I noticed last night that the Camera app does not seem to be doing any auto-focusing, or if it is, it is doing a spectacularly bad job of it. Has anybody else had problems with camera focus lately?
[T-Mobile myTouch 4G Slide] acwest:
Kernel versions

I finally got clever enough to figure out the git tags for the 007 and 1.5 kernels (Emanuel put part of the git hash in the kernel version strings). Luckily, 1.5 runs long enough on my phone that I could get the kernel version. So the last known good version is based on Kernel 3.0.93, with hash f00285ec1ada6ede18ca4d668758bed61470eb39, and 1.5 is the first known broken version, with kernel 3.0.97 hash ec13d5dc923a27f8bc2c959027ab34d6ab0af4c2

Of course, now comes the hard part, I imagine there were more than a few changes upstream from 3.0.93 and 3.0.97, but it should keep me busy...
[T-Mobile myTouch 4G Slide] abe5:
Dirty-flashed v1.7 over v1.6 and no issues to report. Thanks. :)
[T-Mobile myTouch 4G Slide] Paitor:
Maby the same issue in jellykang 2.1? [MENTION=904756]bengmau[/MENTION] seems to have similar issues.
[T-Mobile myTouch 4G Slide] innovativedishcloth:
For some reason I cannot flash any version of this ROM higher than 1.4

I originally flashed 1.3, and dirty flashed to 1.4 with no problems, everything I use works great.

However, when I flash 1.5 or 1.7, I get an infinite boot loop. Sometimes it makes it to the spinning CM logo for a second, but not usually.

I tried both dirty flashing and clean flashing 1.5 and 1.7 all with the same result.

I see some people talking about the kernel.

According to "about phone" I have 3.0.94-WildKernel-reloaded....

Also, I am Revolution unlocked, S-Off, and the 1.44 Hboot.

Am I missing something? I would love to use the new versions.

Thanks.
[T-Mobile myTouch 4G Slide] acwest:
It appears that some sort of issue affecting a few of our devices crept in between 1.4 and 1.5. If you install 1.5, and install WildKernel-Reloaded 007 over top of it, it should work. I have a slightly modified version of 007 (I pretty much just changed the installer to work with 4.3.1 as well as 4.3) which will work with 1.6 as well, although there is a different problem with 1.7, so we haven't been able to get that to work.

If you can run the command:

adb shell cat /proc/last_kmsg > kmsg.txt

on your device while it is boot looping (probably while the Cyanogen Mod circle is spinning) the contents of kmsg.txt may help me track it down.

Actually, your information is helpful to me, as it looks like the kernel in 1.4 is newer than WIldKernel 007, which helps narrow things down a bit. Can you send me the rest of the kernel version string?

I am currently going through all of the differences between a working and non-working kernel, line by line, looking for something that can explain this behaviour...
[T-Mobile myTouch 4G Slide] innovativedishcloth:
My full kernel string in "about phone" on my working 1.4 is:

3.0.94-WildKernel-reloaded-g6463139

utomi@Ubuntu-Downstairs #1

Wed Sep 4 18:47:57 CDT 2013

I'll get the kmsg as soon as I can afford to experiment again (this is my daily driver phone, so I actually need to use it sometimes!)
[T-Mobile myTouch 4G Slide] Vauvenal7:
So, after like an eternity (round 2months now) i got this ROM as a DD

I love it, its one of your finest ROMs ever made (jellykang is nice too, but i still havent found out why i cant activate halo^^)

The only thing i got in those 2 months are really random reboots every once in a while (sometimes 3 times a day, other times once in 3 days)

No clue why, a bit annoying, but not that much of a deal

Great ROM and thanks for all the hard work :D

Greets Vauvenal7

Sent from my MyTouch 4G Slide
[T-Mobile myTouch 4G Slide] Limewirelord:
Google Experience Launcher works fine besides the search function consistently crashing whenever you enter a search query.
[T-Mobile myTouch 4G Slide] Dukenukemx:
Anyone know if the Freedreno drivers can be used? Don't hate me if it's a stupid question.
[T-Mobile myTouch 4G Slide] steve_77:
Bad links ...

Emmanuel U,

On first page

links are not working. :(

also what is the difference between "slim" and "full", if im not mistaken (from reading various posts) it would appear that that i wont be able to use the the new maps and must use the old maps [MENTION=4519508]http://[/MENTION]goo.gl/Asll7 (i.e. Maps_6_14_4.apk )

is this correct?
[T-Mobile myTouch 4G Slide] Vauvenal7:
Weird...flashed 1.7 from scratch (with full wipe and all) and now it reboots when i want to sign into dropbox

Anybody any idea?

Greets Vauvenal7

Sent from my myTouch_4G_Slide
[T-Mobile myTouch 4G Slide] acwest:
If you have adb installed and enabled, can you get the output of:

adb shell cat /proc/last_kmsg

after one of these reboots?
[T-Mobile myTouch 4G Slide] Vauvenal7:
Huh, weird oO

I changed ROM for a day, and went back (via nandroid) to try the adb logcat, but it seems as it fixed itself

Could sign in without any problem or reboot

No plan what was at the first time (tried it 3 times, always a reboot, and now nothing :D )

Ok, thanks for the help anyway :D

Greets Vauvenal7

Sent from my myTouch_4G_Slide
[T-Mobile myTouch 4G Slide] acwest:
I call it the mechanic effect. Nothing like threatening something with a mechanic to get it to start working on it's own...
[T-Mobile myTouch 4G Slide] Vauvenal7:
Well, now the mobile internet seems to have a bug oO

Cant connect to the internet (reboot didnt fix it though :/ )

What to do now? :S

Greets Vauvenal7

Sent from my myTouch_4G_Slide
[T-Mobile myTouch 4G Slide] acwest:
I frequently get this problem, but here it seems to be caused by having a second APN for MMS. If you only have one APN, its not the same problem. If you do have an MMS APN, try disabling it
[T-Mobile myTouch 4G Slide] steve_77:
any special directions for flashing

Forgive my ignorance and frustration here, but ive been trying to get this rom installed. I first started out flashing DS JB 1.7 last night - i was running mikrom 0.7(GB) - wiped the while device, stats, cache, factory reset, then flashed DS 1.7 - but the device seems to be stuck hanging at the factory boot up page for hours -you know with the white background with "T-Mobile MyTouch 4G slide" .

I recall hearing issues of people trying to flash 1.7 directly and not doing an upgrade from some previous version of JellyBean DS... but was hoping for some guidance...

it seems im having the same issue as :

However - I also tried rewiping and flashing 1.4 and 1.3 - which give me the same problem. Frustrated i wiped it all again flashed the wildkernel 8, and tried then flashing the same 1.7, 1.4 and 1.3 with a full wipe inbetween, granted im still running GB and its been a long time since ive flashed a rom, but something is amiss and i can really use some help. I dont even get to the CM spinning logo..

my scenario (PREVIOUS to FLASHING the DS JB 1.X and WildKernel 8):

Miktouch 0.7 (gingerbread)

doubleshot PVT SHIP S-OFF RL

Hboot-1.45.0013

radio-11.16.3504.20_2

eMMC-boot

nov 21, 2011

CM recovery 5.0.2.7

as i said i tried flashing a few (with full wipes in between) of the DS JB rom without success...

As i was running GB near stock, I have not experimented with any alternate kernel, so thought that perhaps it was needed, so i:.

a) flashed new kernel (wildkernel 8)

b) flashed jellybeanDS 1.4 (on top)

c) rebooted & noticed it was stuck at white "tmobile my touch slide " screen.... so regardless i pulled battery and

c) dirty flashed jellybeanDS 1.7 on top thinking it might fix the issue but no go

it seems like i always get stuck at white screen boot screen that has the fancy "T-Mobile MyTouch 4G slide" text on it no matter what i try.

Given that my device is pretty much wiped, is there a log file somewhere i might be able to post to help solve this issue?
[T-Mobile myTouch 4G Slide] acwest:
To eliminate the kernel issue some of us have been having, I recommend starting with version 1.4 of this ROM. Before flashing, wipe data, wipe cache, wipe dalvik cache, and format system, then flash the 1.4 ROM. Does it do anything at this point?

---------- Post added at 03:23 AM ---------- Previous post was at 03:13 AM ----------

I thought I would post an update here... With some help from Emmanuel, I have now successfully built the kernel from version 1.4 of this ROM and am running it on my phone, over the 1.6 ROM. 1.4 seems to be the latest released kernel that works on my device. I was not able to put WildKernel007 over the 1.7 ROM, I suspect it needs a newer version, although I haven't actually tried with the 1,4 Kernel, which is slightly newer than 007. The next step is to go through each checking on the tree until I find when the kernel causes my device to hang/reboot. Hopefully I will have the bug tracked down by the weekend, so I can get caught up to the latest version of the ROM and Kernel :)
[T-Mobile myTouch 4G Slide] steve_77:
I have had no luck with kernels included in the DS JB 1.3 rom. the 1.4 rom and the 1.7 rom.

I also tried the JellyKang 2.1 and 2.0 all of which get me stuck in a bootloop.

I then tried the WildKernel with 1.4 JB DS as well as 1.7 wirh same result- i went back to miktouch 0.7 (GB) without issue

I do full wipe between installation attempts (cache, data, system, sdext, dalvik)

Recalling how some roms i the past didnt work right if you did not have the right recovery i updated my recovery to CM 6.0.3.3 - and tried again to no avail. I surely though the 1.4 rom would work as is but it was just nt meant to be at least on my device.

I then came across another thread on others being stuck in bootloop and im sure I am having the same issue :(

Any resolution to this issue would be great, im so jealous of those that got this rom working on their devices and here I am... stuck with GB 2.3.4 :(
[T-Mobile myTouch 4G Slide] acwest:
If you can get it to go to recovery while it is boot-looping, you might be able to get the last_kmsg file.. If: adb shell cat /proc/last_kmesg

returns anything, it would be very helpful in figuring out why it is dying.
[T-Mobile myTouch 4G Slide] steve_77:
Thanks for the tip, after some extensive experiments im going to have to apologize to you all as the issue is not related to this ROM. I cant seem to flash any 4.2 or 4.3 ROM. :( really dont know whats wrong and want to keep this thread clean. moving this issue to the previously mentioned bootloop problem thread.

thanks again.
[T-Mobile myTouch 4G Slide] acwest:
Kernel problems fixed, but phone app still crashes

I posted an update to the WildKernel Reloaded thread, I have successfully gotten the kernel to work on my device. It turns out that after 1.4 some higher CPU frequency settings were baked into the kernel config file, and my phone (and a few others) apparently can't take that.

I tried updating to 1.7 with the new build of the kernel, but I still get the same problem I did before of the Phone App crashing repeatedly. I suppose my next project will be debugging that, but for now I am using 1.6 with the 1.7 kernel (and lower speed).

Thanks to everyone who helped, especially Emmanuel, who both put together the kernel in the first place, and got me a build of the tool chain so I could find the problem :)

-Craig
[T-Mobile myTouch 4G Slide] tbalden:
Are you s-off? You need to flash the kernel boot.IMG from fastboot if you are s-on unlocked only. To flash it from recovery you must be s-off
[T-Mobile myTouch 4G Slide] steve_77:
My hboot menu says im S-OFF - would it hurt if i reran my device through revolutionaryio - could this cause any issues?

my hboot menu:

doubleshot PVT SHIP S-OFF RL

Hboot-1.45.0013

radio-11.16.3504.20_2

eMMC-boot

nov 21, 2011​
[T-Mobile myTouch 4G Slide] tbalden:
seems fine, if it says S-off, you shouldn't rerun it..so it's rather strange it doesn't work for you. :confused:
[T-Mobile myTouch 4G Slide] steve_77:
yeah I dont know either been driving me crazy - tried 3 different recoveries, several different ROMS, I posted some recovery logfiles at

the bootloop thread if anyone wants to take a stab at it.

Just dont want to sidetrack this thread as def looks like a device problem. If anyone has any suggestions please post here instead - thank you all very much
[T-Mobile myTouch 4G Slide] Emmanuel U:
[MENTION=2878915]SilverL[/MENTION] and I were able to get Android 4.4 booting tonight, however it is

extremely

un-usuable (I couldn't even get a screenshot like I usually like to :(). The touchscreen and buttons seem partially unresponsive (that may be from the main system segfaulting) and adb seems to shutoff after a few seconds post-boot. Then processes start to force close and system segfaults. However a few things do work from what I've noticed from how little it can be used; lights (LED and button lights), Radio/RIL, Sound? Those are what are fully confirmed working. You can find our source here and more work w/ debugging will be put into this tomorrow and in the next days. Good night everyone
[T-Mobile myTouch 4G Slide] _crAss_:
Big thanx for your time and effort to get kitkat to our devices!
[T-Mobile myTouch 4G Slide] SKAm69:
Yeah, thanks for working on it. Kitkat is the most major update for the past 2 years. I'm very exited about it

BTW I saw guys at Sensation section got CM11/4.4 functional maybe some of their work can be useful for Doubleshot
[T-Mobile myTouch 4G Slide] steve_77:
Sorry but what version of Hboot is needed with this ROM ?
[T-Mobile myTouch 4G Slide] Emmanuel U:
Doesn't matter, as long as you have a custom recovery (preferably TWRP) you're fine
[T-Mobile myTouch 4G Slide] killkillkill:
No, 4.0 retains that honor (was 4.0 release within the last 2 years? Why yes... it was...)

4.4 is actually the smallest/easiest update among 4.x yet.

4.2 --> 4.3 was a bigger update.

4.1 --> 4.2 was bigger yet.

4.0 --> 4.1 was bigger still.

2.3 --> 4.0 was massive.

When we worked Relay from 4.3 --> 4.4, it was a bigger battle convincing the build server to do its job, than the actual device work. The device stuff all "just worked".

Yes, it will be tougher for doubleshot, because its hardware support is no longer being actively developed by qcom.
[T-Mobile myTouch 4G Slide] abe5:
Agreed. What makes KitKat appealing to me is the ahead-of-time compiler and the supposedly optimised support for "low-end" devices. :)

And still, this JellyBean DS flies on my phone. Our devs rock. :D
[T-Mobile myTouch 4G Slide] _crAss_:
Support for lower end devices from what I have read around is going to be based on actual task killing...the thing that everybody said you should never do in an android device. Before the doubleshot I had a Motorola Milestone (the initial version) with only 256 MB of ram and due to some great developers we were able to run CM10, but the memory management needed extreme fine tuning and tweaking in order to make it work.

Right now running the latest Jellykang everything is great and the only app that seems to suck ram is facebook messenger...Other than that, whatever I am running is simply ok. Greenify also helps big time if you don't want apps to run whenever they want instead of whenever you want and finally I have disabled automatic starting with the device of apps with Autostarts. With this configuration I always have at least of 150 MB of free ram even after days from rebooting...

Hopefully we will also get KitKat and it will be great. Thanx to the developers again!
[T-Mobile myTouch 4G Slide] killkillkill:
Android loads and kills processes on its own all of the time. What you are not supposed to do is introduce additional automated process killing... processes, because when something besides android itself kills the process, it frees up ram, so Android responds by filling that ram by loading processes that it thinks you will need.

The difference here is that Android will remain in charge as it should be, so when it determines that a process needs to be killed, it won't just load something else in its place.