Database Develop

[FIXES] Milestone Latest WIFI Module for 02_36 kernel

Latest and stable Wifi Driver for Android 2.1, Build SHOLS_U2_02.36.0
Build for the kernel "2.6.29-omap1"
** Stable and without any Wifi drop problem, which is compiled from the latest source from Google Android Repository. **
I recently found out that the Wifi driver of the latest Froyo 2.2.1 of Milestone that released by G.O.T. team is a new build and very stable. Therefore, I tried to pull the latest TIWLAN Wifi driver source code from the Google Android Source Repository (http://android.git.kernel.org/?p=platform/hardware/ti/wlan.git;a=summary), and compile it for the ROM build "SHOLS_U2_02.36.0", kernel "2.6.29-omap1".
I succeeded to compile as "tiwlan_drv.ko", and use it with the latest firmware "fw_wlan1271.bin" from the Froyo 2.2.1 build, and finally uses on the "SHOLS_U2_02.36.0", and the result is very stable wifi connection with the proprietary power saving feature .
I am using the ROM South Asia SHOLS_U2_02.36.0, I am not sure if it can be used with any other ROM, but normally should work on any kernel which have the version "2.6.29-omap1".
I did it because that the latest Froyo 2.2.1 beta ROM is not stable enough and the battery drain fast, but it have the stable wifi connection, so I compiled it for 2.1.
Enhancement:
Much more stable WIFI connection, no more connection drop within good signal environment.
No more WIFI freeze occur, will auto re-connect to AP if back to the signaled environment.
Much much much more battery saving (IT IS THE MOST IMPORTANT), can also feel that impressively in using "android-wireless-tether".
!!! Use it at YOUR OWN RISK !!!
Make a backup of "/system/lib/modules/tiwlan_drv.ko" and "/system/etc/wifi/fw_wl1271.bin".
Copy the file "tiwlan_drv.ko" to "/system/lib/modules/", and copy the file "fw_wl1271.bin" to "/system/etc/wifi/".
** WARNING **
Normally should work on any ROM which have the kernel version "2.6.29-omap1", BUT I didn't test it for any ROM other than SHOLS_U2.02.36.0, so USE IT AT YOUR OWN RISK!!!
It may result in bootloop in case if you did something wrong or not compatible with your ROM (need to revert back to the old driver with OpenRecovery + adb).
Therefore, it is only for advanced users, and ALWAYS MAKE FULL BACKUP of your milestone.
Download link:
http://www.sendspace.com/file/ln3xm7

Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[EDIT]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
[EDIT2]Woo! Works!

Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[Edit]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
Click to expand...
Click to collapse
"fw_tiwlan_ap.bin" is the firmware required for the Froyo 2.2.1 to use Wifi Hotspot, it did nothing on Android 2.1, so just simply ignore it.
and Thanks for pointing out the location of placing the "fw_wlan1271.bin" file, I will modify it.

Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb
[EDIT2]Woo! Works!
Click to expand...
Click to collapse
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version

How can I copy and paste to the system?
Thanks!

royshum said:
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
Click to expand...
Click to collapse
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
How can I copy and paste to the system?
Thanks!
Click to expand...
Click to collapse
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot

Lollipop_Lawlipop said:
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Click to expand...
Click to collapse
failed to copy - read only!

chungtau said:
failed to copy - read only!
Click to expand...
Click to collapse
You must have a rooted milestone in order to process.
Before you using adb push, try to remount your /system partition first.
Or you can try the following commands.
Ensure your wifi is turned off first.
*** Remember to make FULL BACKUP for your milestone before proceeding the following commands. ***
Code:
C:\android-sdk-windows\tools>adb push tiwlan_drv.ko /sdcard/tiwlan_drv.ko
C:\android-sdk-windows\tools>adb push fw_wl1271.bin /sdcard/fw_wl1271.bin
C:\android-sdk-windows\tools>adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
# cd /system/lib/modules
# mv tiwlan_drv.ko tiwlan_drv.ko.bak
# cp /sdcard/tiwlan_drv.ko ./tiwlan_drv.ko
# chmod 644 tiwlan_drv.ko
# cd /system/etc/wifi
# mv fw_wl1271.bin fw_wl1271.bin.bak
# cp /sdcard/fw_wl1271.bin ./fw_wl1271.bin
# chmod 644 fw_wl1271.bin
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
And now, you can try turning on your wifi.
In case if there is any problem occurred, you may reboot into OpenRecovery, revert the drivers from "tiwlan_drv.ko.bak" and "fw_wl1271.bin.bak".

I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.

I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror

Lollipop_Lawlipop said:
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
Click to expand...
Click to collapse
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network .
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
You haven't read the instructions carefully. It is the latest wifi driver for "2.1", not "2.2.1", as it is supposed to compile the driver from "2.2.1" down to "2.1".
So for 2.2.1, by default, you are already have the latest wifi driver (at least a stable wifi driver), it is no clue for using it.

royshum said:
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network :
Click to expand...
Click to collapse
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Btw, CM6 uses the file name fw_wlan1271.bin. I'm guessing stock Android from Moto looks for fw_wl1271.bin (just guessing... can't exactly prove it since I'm not running stock Android), which was why I was trying to correct you (although it seems to me both of us are right).
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
If you're running 2.2.1-CM6 you can extract the files from the update zip and adb push them into the phone. That is, if you're on CM6. If not, well... you can either upgrade to CM6 or go into fastboot and restore the sbf again.

Lollipop_Lawlipop said:
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Click to expand...
Click to collapse
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data

MenoDev said:
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Click to expand...
Click to collapse
Yes, I have the same suspicion as well.
MenoDev said:
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
Click to expand...
Click to collapse
Can you go into a bit of detail on that? I'm interested
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.

works flawless, extreme improvement, thank you very much!

Lollipop_Lawlipop said:
Yes, I have the same suspicion as well.
Can you go into a bit of detail on that? I'm interested
Well, I use to code similar stuff but I am complete new to android so i have to read the dev guide, if I had no guide I'd probably create a dump, see according the file descriptor where the tables and storage are are located, then set a "write" flag on the file system and flush it to avoid a manual battery pull. but i'm sure there's more elegant ways.
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
Click to expand...
Click to collapse
I made a little research and found a working solution, tested it myself.
Apparently it can happen that the resolved DNS can not be stored under certain circumstances, (in order to trace those, i try to avoid the "out of the box" mods, even though the guys make a tremendous job, but i feel more secure and have a higher learning curve by doing stuff myself).
In order to avoid random disconnects from network or wifi, or worst case both, add the following lines of code to /system/default.prop
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
These are the google dns, most probably the best choice. You can find this out if you fire up the "getprop" command.
I've seen that most Recovery tools such as the G.O.T one, have implemented the DNS fix, but personally I prefer to just fire up a terminal from the phone and add these lines manually with some comment, so i know what and why I'm doing stuff.
Hope this helps, let me know.

Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it didn'tsolve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0

b787 said:
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it solve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
Click to expand...
Click to collapse
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?

MenoDev said:
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
Click to expand...
Click to collapse
I did turn off wifi before copying any files. However, I didn't rebooted before I tried to start wifi, only after I noticed it doesn't work.

Fix for 2.2.1 Possible?
I have the same issue with my home WIFI network on 2.1 and 2.2.1: namely the connection drops during large transfers (such as a Market app download) and I have to turn WIFI off and on again to have connectivity again.
I wonder if 2.2.1 really has the latest firmware baked in...how would I compile the TI firmware for 2.2.1?

[MOD] Webtop over HDMI Hack for Atrix GB 2.3.4 (HKTW, AT&T 4.5.91, ORFR 4.5.2A)

I am pleased to announce that I've patched the Atrix webtop files, allowing us to run webtop over HDMI on HKTW, AT&T 4.5.91 and ORFR 4.5.2A based system images (yes this will work on custom ROMs too), without the requirements of an official dock!
The goal is to enable the Webtop function over HDMI on any display, not just official Motorola Docks. There seem to be more HDMI display options that are disabled, for example: Clock Widget, Gallery, Music, Home. Sadly, none of these options actually do anything on the big screen, they just display the interface on the phone
However, Webtop works great! Just use the instructions below to replace the original DockService and PortalApp apk's.
Included are two versions of the DockService in the zip attached to this thread, one will enable only the additional Webtop mode for HDMI. The second one will be a "dev" version that enables every option, for those of you that are curious and/or want to try to get some of them to work over HDMI! Only one version of PortalApp is included, which is required for webtop to work, with both versions of the DockService.
One particularly interesting option that many of you are interested in is included in the dev build too: Mirror phone on display . Sadly, as stated above, it does not work (yet?). Will you get it to work?
Requirements:
Have one of the supported build and functional webtop flashed
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
adb push DockService.apk /sdcard/
adb push PortalApp.apk /sdcard/
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mv /system/app/DockService.apk /system/app/DockService.apk.bak
mv /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
cd /system/app
cp /sdcard/DockService.apk ./
cp /sdcard/PortalApp.apk ./
chown 0:0 ./DockService.apk
chown 0:0 ./PortalApp.apk
chmod 644 ./DockService.apk
chmod 644 ./PortalApp.apk
reboot
NOTE: if these instructions dazzle you, try Ronaldo's CWM package (for AT&T only!): http://forum.xda-developers.com/showpost.php?p=15871616&postcount=53
NOTE2: ignore errors concerning odex files if you are deodexed.
NOTE3: If you have issues with the Touchscreen Input not working, try a reboot first. If the problem doesn't go away: fastboot flash a (stock) webtop image for your base ROM. It is currently unclear what causes this problem, but my guess is a bad flash of the webtop partition, possibly CWM related. Reboot/reflash has solved the problem for a few people encountering this issue.
Thanks to Gizmo, eval & romracer!

More information on dev version
Some extra information on the different modes that are available (but currently non-functional):
Clock: Transform your phone screen into a big clock with perks. See the time from afar, set alarms, play music, view photos and get live weather information. This mode was designed for your bedside but is useful in the kitchen and as a desk clock too.
WidgetDock: Get access to the same Android widgets, apps and shortcuts as on your phone home screen. Arrange them and change the wallpaper to your liking. All of which will be saved and applied the next time your dock your phone.
Mirror: Access and display all of the phone applications on a larger display
Other: Displays non-smart mode dock apps
Gallery: View photos and videos
Music: Access, listen, and share music
There is also mention of an "easport" option, with the following description: "Entertainment detailed description goes here. To be added later."
Although not working currently, they give a good insight in what is to come

IMO, one of the best features of the Atrix right here. You're the man!

Great, I was looking forward to this. Thanks again.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.

_unknown said:
Today, I am pleased to announce to you a modified DockService.apk which allows us to run webtop over HDMI on HKTW, without the requirements of an official dock!
...
Major thanks go to a friend who prefers to stay anonymous, but was key in solving this problem! And as always thanks to the ever-helpful eval- for his assistance
Click to expand...
Click to collapse
Bull****, this was all you!! Awesome work, BTW =) Excited to go back to 2.3.4!

Touch pad controls dont work for me

Everything works fine

Holy **** ! That is all.

So, frist, thanx for this excelent work! Now my webtop works.
I just have one problem, my mousepad on lapdock doesnt work!

works great! thanks!

Awesome work! I only used my atrix for a few minutes before flashing 2.3.4 so I have no idea how well this worked before, but I'm pleased. All I know is when I plug in the HDMI, it restarts into the webtop mode and it works well from there. The entertainment center app crashes but that isn't as a result of this, it definitely did that when I tried to run it before.

mouse not working
loads fine but no mouse control for me either..

Same for me. The webtop loads up fine, but no mouse control on the touchpad.

_kansei_ said:
Awesome work! I only used my atrix for a few minutes before flashing 2.3.4 so I have no idea how well this worked before, but I'm pleased. All I know is when I plug in the HDMI, it restarts into the webtop mode and it works well from there. The entertainment center app crashes but that isn't as a result of this, it definitely did that when I tried to run it before.
Click to expand...
Click to collapse
Does your mouse work ? A majority, myself included, it does not ....
For the ones whose touchpad does not work.
Did you install the CG61.img or do the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix?
I'm using Rollup tried version 1.4 and 1.5. Touchpad is broke ****.

dicksteele said:
Does your mouse work ? A majority, myself included, it does not ....
Click to expand...
Click to collapse
I was having the same problem with the mouse I fixed it by reflashing webtop from fastboot.
Sent from my MB860 using XDA App

NYG-SBXLII said:
I was having the same problem with the mouse I fixed it by reflashing webtop from fastboot.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Before I read your reply I said wtf and tried that before I gave up for the night and that was my fix also.
Now to start hacking it and get lxterminal going.
Thanks !!!

dicksteele said:
Does your mouse work ? A majority, myself included, it does not ....
For the ones whose touchpad does not work.
Did you install the CG61.img or do the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix?
I'm using Rollup tried version 1.4 and 1.5. Touchpad is broke ****.
Click to expand...
Click to collapse
if by touchpad you mean using the screen of the phone as a touchpad, it's working fine. I don't have a lapdock to test, but I could walk over to the AT&T store in the AM to check it out.
Edit: if that is the case, and something is working on my Atrix but not on many others, I assure you it was just a lucky accident. I may be a systems engineer by date but by night I'm little more than an Android n00b. I'll gladly poke around on my device to collect info that might help others get their webtops sorted.

I successfully flashed the webtop and the touchpad is working fine. But I did notice at times, GUI became unresponsive to the touchpad (touchscreen). It it not perfect, but it works

See now this almost makes me wish I still had my Atrix...
I would love to tinker around with these APKs some more. Especially with the new options cropping up.
But, as it is I am doing it all blind... doing DEV for a phone you don't have is tricky business.

Awesome!! Worked perfect!
Installed using ADB via OP commands. Never flashed the CG61.img or the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix and I am having absolutely NO problems using the screen as the mouse pad.
Make sure you followed all commands and set the permissions correctly with the chmod command.
No problems at all here, but I did flash the non-dev apk.... if you flashed the dev apk then that may be where the mouse pad issue is, I can not confirm.

[Q] Kindle Fire HD 7 2012 rooted with cyanogenmod 11 keeps restarting

Hi, I have two Kindle Fire HD 7 inch, I think both are the older model. Until recently, one was bricked after i rooted but it started getting random restarts after being fine for months. I decided to try flashing a custom ROM, but due to following a YouTube video and not loading the ROM first before flashing, my fault as I mid heard the instructions, it died and I didn't know enough to reliase it could be fixed with a factory cable. I got a replacement and due to a **** up at Amazon, I managed to keep the broken one also.
I decided to root the newer one a few weeks in but months later it started having issues with dolphin browser constantly restarting, so I decided to buy a factory cable as a precusion and flash it to cyanogenmod. Everything went well so i dawned on me that I could fix the first one with my cable. I managed to fix with instructions from here and then flashed as well. Everything seemed to work fine until it started randomly restarting. Then it would get stuck at the blue kindle logo, would still allow me into twrp, so cleared dalvik and everything else and reflashed, it would load as newly flashed, but end up restarting again and eventually getting stuck at the blue logo again. I've seen a few threads with similar problems but couldn't find one that matched the circumstance.
So, my question, it this likely a hardware issue as it did get dropped once or twice in its short working life, or is it a software issue and something I could fix ???

damofitz said:
Hi, I have two Kindle Fire HD 7 inch, I think both are the older model. Until recently, one was bricked after i rooted but it started getting random restarts after being fine for months. I decided to try flashing a custom ROM, but due to following a YouTube video and not loading the ROM first before flashing, my fault as I mid heard the instructions, it died and I didn't know enough to reliase it could be fixed with a factory cable. I got a replacement and due to a **** up at Amazon, I managed to keep the broken one also.
I decided to root the newer one a few weeks in but months later it started having issues with dolphin browser constantly restarting, so I decided to buy a factory cable as a precusion and flash it to cyanogenmod. Everything went well so i dawned on me that I could fix the first one with my cable. I managed to fix with instructions from here and then flashed as well. Everything seemed to work fine until it started randomly restarting. Then it would get stuck at the blue kindle logo, would still allow me into twrp, so cleared dalvik and everything else and reflashed, it would load as newly flashed, but end up restarting again and eventually getting stuck at the blue logo again. I've seen a few threads with similar problems but couldn't find one that matched the circumstance.
So, my question, it this likely a hardware issue as it did get dropped once or twice in its short working life, or is it a software issue and something I could fix ???
Click to expand...
Click to collapse
i can take a few guesses at what would be causing a random reboot, i know dolphin can, i don't know why you would need to reflash to fix it though, thats very unusual unless maybe a filesystem error was causing it but it shouldnt have the same error everytime, i could suggest scanning the system partition for errors from recovery, i'd have to grab the command you'd need to run through adb. you dmesg would tell you if there were filesystem errors probably, mine was telling me about them so i finally got around to fixing them. i will mention i know dolphin can cause it to reboot randomly, i have had it happen before, i think it draws too much power trying to run it and causes the crash, not positive though.
On a side note you may want to rename the thread to 2012 kindle, the 2013 one is not rom-able, only rootable.
Did you overclock the processor?

stunts513 said:
i can take a few guesses at what would be causing a random reboot, i know dolphin can, i don't know why you would need to reflash to fix it though, thats very unusual unless maybe a filesystem error was causing it but it shouldnt have the same error everytime, i could suggest scanning the system partition for errors from recovery, i'd have to grab the command you'd need to run through adb. you dmesg would tell you if there were filesystem errors probably, mine was telling me about them so i finally got around to fixing them. i will mention i know dolphin can cause it to reboot randomly, i have had it happen before, i think it draws too much power trying to run it and causes the crash, not positive though.
On a side note you may want to rename the thread to 2012 kindle, the 2013 one is not rom-able, only rootable.
Click to expand...
Click to collapse
Sorry, your right, its the 2012, I just noticed that the 2013 doesn't have a front camera. As for dolphin, I uninstalled a bunch of times with the same result, but I like it because the flash player works well once set up properly. It always starts off fine then gets progressively more unstable on my working kindle. I don't know much about adb, just the basics but have KindleFireFirstAid and other programs that used the fix permission errors. I haven't got round to trying them get though as the kindle normally wont stay on long enough.
When it was just rooted, the kindle would still restart so I was hoping that flashing might fix it in case it was something I had done wrong.
Oh, and I haven't over clocked, I signed into play store and allowed it to download all my girlfriends crap so she could use it for a while while her galaxy tab goes into the shop as it has the red charging cross issue.

damofitz said:
Sorry, your right, its the 2012, I just noticed that the 2013 doesn't have a front camera. As for dolphin, I uninstalled a bunch of times with the same result, but I like it because the flash player works well once set up properly. It always starts off fine then gets progressively more unstable on my working kindle. I don't know much about adb, just the basics but have KindleFireFirstAid and other programs that used the fix permission errors. I haven't got round to trying them get though as the kindle normally wont stay on long enough.
When it was just rooted, the kindle would still restart so I was hoping that flashing might fix it in case it was something I had done wrong.
Click to expand...
Click to collapse
you mind booting it up into a os and running this from a command prompt?
Code:
adb shell dmesg > log.txt
you will need to have a command prompt cd'd into the directory of adb, so either in a kffa folder or srt folder will do, anything that came with adb really. if you don't know much about command prompt then do this: shift + right click the folder with adb, hit "open command window here", then run that command.

stunts513 said:
you mind booting it up into a os and running this from a command prompt?
Code:
adb shell dmesg > log.txt
you will need to have a command prompt cd'd into the directory of adb, so either in a kffa folder or srt folder will do, anything that came with adb really. if you don't know much about command prompt then do this: shift + right click the folder with adb, hit "open command window here", then run that command.
Click to expand...
Click to collapse
I normally go from the SDK platform tools folder to check the device is coming up, does that work?

damofitz said:
I normally go from the SDK platform tools folder to check the device is coming up, does that work?
Click to expand...
Click to collapse
Ok, i tried and it and it just shows the command line again. Have killed and restarted server but no difference
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb devices
List of devices attached
D025A0A024060MRL device
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb shell dmesg > log.txt
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>
update: I have noticed that when plugged into my laptop, the Kindle will stay on indefinitely, but when I unplug or not long after, the Kindle then restarts, especially when im doing something like searching the web or opening apps, so could it be a power source problem?

damofitz said:
Ok, i tried and it and it just shows the command line again. Have killed and restarted server but no difference
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb devices
List of devices attached
D025A0A024060MRL device
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb shell dmesg > log.txt
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>
update: I have noticed that when plugged into my laptop, the Kindle will stay on indefinitely, but when I unplug or not long after, the Kindle then restarts, especially when im doing something like searching the web or opening apps, so could it be a power source problem?
Click to expand...
Click to collapse
i probably should have mentioned that the commadn i asked you to run was outputting the text into a file called log.txt in the same folder you ran the commadn in... plz post it as a attatchment. sorry for my stupidity.

stunts513 said:
i probably should have mentioned that the commadn i asked you to run was outputting the text into a file called log.txt in the same folder you ran the commadn in... plz post it as a attatchment. sorry for my stupidity.
Click to expand...
Click to collapse
No need to apologize. I left the table on all night and its still on this morning. The log is attached

damofitz said:
No need to apologize. I left the table on all night and its still on this morning. The log is attached
Click to expand...
Click to collapse
think the filesystem is ok not seeing any errors...another thing you could do is leave the device plugged into the pc with this running
Code:
adb shell "su -c 'cat /proc/kmsg'"
and whenever it reboots just copy and paste the last lines it outputted.

[App] Cast Receiver app for Android

UPDATE 27th November 2014
I have added an Xposed module for the clients below that will work around the issue with Google Play services 6.5
UPDATE 25th November 2014
Google have released Google Play services 6.5 which has strengthened security, effectively making this app useless (clients will be unable to connect). Until Google either loosen the security (which is unlikely to happen), or someone somehow were able to get a hold of the private keys from the chromecast/Android TV this app will no longer work and will no longer be updated.
Thank you all for your support!
Hi everyone! I've decided to finally release my modified Cast Receiver app from the ADT-1 for Android that will work on most devices (though not sure what the minimum api requirement is).
If you don't know what this is it's basically a chromecast receiver for your Android; I use it on my Android mini PC that's hooked up to my TV.
Downloads
Last updated Nov 05 2014.
Recovery install (requires KitKat or newer, or the Xposed module below)
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiaU5WSWRxeC02Tzg
Signed
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiVDR1a1o0WFVSWjg
System install (requires KitKat or newer, or the Xposed module below)
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiNFJGUE1acGZTeFE
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiOTRoanlyX19pVmc
If you are not rooted and can only install it as a regular apk, use the signed version. Note however that casting the screen from another Android device will not work due to a signature mismatch (Google Play Services checks the signatures of the app before allowing screencasting).
If you are rooted you should go for the recovery/system install option, as that will allow screencasting to work.
Xposed module for receiver
If you want to be able to use the system install version on devices older than KitKat you can use the following Xposed module:
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiZEFrN1RqLTRFdkk
Xposed module for client
Version 6.5 and newer of Google Play services makes it impossible to connect to the receiver due to some added security. This Xposed module works around that:
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiWG1tU3NfYWwwV00
Install
Recovery install
No special instructions needed, simply copy SYSTEM-CastReceiver.zip to the internal storage (or sdcard) on your device and flash it through your recovery (follow the instructions for your specific recovery).
Signed
Simply install the apk as you would with any apk, either through adb:
Code:
adb install -r AndroidMediaShell-signed.apk
or by installing it from your sdcard.
System install
You will need rooted adb for this to work correctly.
If you come from an old install, you can safely remove the old lib first:
Code:
adb remount && adb shell rm /system/lib/libmedia_shell_content_view.so
Once that's done, run:
Code:
adb remount && adb push libcast_shell_android.so /system/lib/ && adb shell chmod 0644 /system/lib/libcast_shell_android.so
adb remount && adb push AndroidMediaShell.apk /system/priv-app/ && adb shell chmod 0644 /system/priv-app/AndroidMediaShell.apk
(Change priv-app to app on devices older than 4.4)
Running
Amazon Fire TV
Because the Whisperplay app implements a DIAL protocol of its own on port 8008, which the Cast Receiver app also uses and that causes a conflict between the two apps.
To get the app running correctly you need to rename WhisperplayCore.apk:
Code:
adb shell mv /system/app/WhisperplayCore.apk /system/app/WhisperplayCore.apk.bak
once that's done, reboot and follow the instructions below.
For the receiver to start you can simply reboot provided you are using the system install. If you are using the signed version you need to run:
Code:
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED -n com.google.android.apps.mediashell/.AutoStartListener
After that it will run automatically in the background after each reboot, so you will be good to go!
Keep in mind that it might take a few minutes for the receiver to show up in the cast list, if it doesn't show after 10 minutes, try rebooting the device.
https://drive.google.com/file/d/0B4FOzj4b2EYiNFRfVDhtZXZGcjg/view?usp=sharing
Supported Apps
Currently not every app is supported. The ones I've tried are:
YouTube - Working
Google Play Music - Working
Google Play Movies & TV - Working
Google+ - Working
Google Photos - Working
Screen Cast - Working (if you follow the instructions above)
Chrome for computer - Working
Netflix - NOT Working (I'm looking into this)
Plex - Working
Chrome for Android - Workinghttps://drive.google.com/file/d/0B4FOzj4b2EYiWVlDTWNGOEw3UTg/view?usp=sharing
Those are the ones I've tried, others may or may not work.
Whether the app will work may also depend on what device you are running the cast receiver on, as well as the region you are in.
FAQ
My device doesn't show up in the official Chromecast app
This is a known "problem" that also affects the ADT-1. There is nothing I can do about it in the Cast Receiver app, only Google can fix it by modifying the Chromecast app. Screen casting etc should work though, it's only the Devices screen that doesn't show any devices.
The receiver doesn't work on my Amazon Fire TV
Please read the instructions under the Running category.
I can't find the receiver device in the cast list
Give it a few minutes. If that doesn't work, try backing out of the app, and enter it again. If it still doesn't show, post a new reply to this thread with a log from logcat.
App X doesn't work
Get me a log when you try to initiate the connection, keeping in mind that some apps may be easier to fix than others. And some may be next to impossible due to them being regional.
How?
I've had some people ask how this was done, so I've written up a list of the changes and a brief summary here:
https://docs.google.com/document/d/1tXnjDdurdoJ4ufulzaqGpuaNpLLt6LGAUk22MO2jta4/edit?usp=sharing
You can get a patch of the smali changes here:
https://drive.google.com/file/d/0B4FOzj4b2EYiTHZBRGVUWmlSV1U/view?usp=sharing
And a bsdiff of the lib changes here:
https://drive.google.com/file/d/0B4FOzj4b2EYiNFRfVDhtZXZGcjg/view?usp=sharing
The source code of the Xposed receiver module can be found here:
https://github.com/HomerSp/XposedCastReceiverFix
The source code of the Xposed client module can be found here:
https://github.com/HomerSp/XposedCastClientFix
And finally here is the code I used while testing the receiver, and writing the MediaDrm and JmDNS code:
https://github.com/HomerSp/CastTest
Changelog
Nov 05, 2014
* Fixed receiver not working while connected to ethernet (may be restricted to the Fire TV)
Oct 29, 2014
* Fixed app not working on API level 15 (tested by me on a real device).
* Disabled logging to file - this should significantly reduce the size of the data that's used by the app.
Oct 26, 2014
* Updated to new 5.0 preview from the ADT-1.
* Lowered API level to 15 on the signed version, keep in mind that this is untested by me. This also includes disabling some DRM API calls that were added in API level 18, so Play Movies will not work on API 17 or lower.
Oct 17, 2014
* Fixed receiver not always starting correctly due to device not being provisioned, thanks to @rkirmeier!
Oct 10, 2014
* First version!
Finally I would like to give out a big thank you to @death2all110 for doing extensive testing for me, as well as providing me with the system dump from the ADT-1. I couldn't have done this without him!
Enjoy!

Great! Works flawlessly on my Ouya (CM11). Run on boot via ScriptManager.

If you need help with Netflix you know where to find me!

Hi,
First of all, thanks, because this works nicely with my laptop! I can finally cast to my living room tv that has an android device connected.
I can cast from Chrome browser (Cast Extension) on OS X, but can't from a 4.2 Android handset (I've tried youtube and google play music). Whenever I try to connect to the Server on a 4.4 radxa rock, the server disappears from the list. It comes back after 10 seconds more or less. Can I help with debug logs or something?
Thanks!

krosk said:
Hi,
First of all, thanks, because this works nicely with my laptop! I can finally cast to my living room tv that has an android device connected.
I can cast from Chrome browser (Cast Extension) on OS X, but can't from a 4.2 Android handset (I've tried youtube and google play music). Whenever I try to connect to the Server on a 4.4 radxa rock, the server disappears from the list. It comes back after 10 seconds more or less. Can I help with debug logs or something?
Thanks!
Click to expand...
Click to collapse
Do you mean 4.2 or 4.4 (you mentioned both)? I haven't tried compatibility with 4.2, but 4.4 should definitely work. In any case, I would need a logcat from the receiver device to be able to see what's wrong.
@death2all110 I probably will, yes. It seems to be restricted to the US for now - I've tried hard-coding a proxy in the code, which makes it go further, but not far enough for it to work. I'll get back to you when I have something for you to test!

HomerSp said:
Do you mean 4.2 or 4.4 (you mentioned both)? I haven't tried compatibility with 4.2, but 4.4 should definitely work. In any case, I would need a logcat from the receiver device to be able to see what's wrong.
Click to expand...
Click to collapse
My phone (4.2) is not connecting to the server (screen) in 4.4. Your app is installed in the 4.4 device. I will send you logs later.

krosk said:
My phone (4.2) is not connecting to the server (screen) in 4.4. Your app is installed in the 4.4 device. I will send you logs later.
Click to expand...
Click to collapse
Of course, I completely misread your post. Sorry!

Nexus Q Install?
Any chance this can be installed onto a Nexus Q - I would love to get my Q-Ball back up and running!

Im not having any luck on a minix 8h (stock rooted rom - 4.4.2) or Note 12.2 running cm11. Same thing happens for me. Devices show up in the list but when you try to connect it fails and that device disappears from the list for a little while. I installed using root explorer by putting the files in the respected folders then setting the correct permissions and rebooting.

rkirmeier said:
Im not having any luck on a minix 8h (stock rooted rom - 4.4.2) or Note 12.2 running cm11. Same thing happens for me. Devices show up in the list but when you try to connect it fails and that device disappears from the list for a little while. I installed using root explorer by putting the files in the respected folders then setting the correct permissions and rebooting.
Click to expand...
Click to collapse
What version of Google play services do you have installed on the sender device? Also, a logcat from the receiver would be useful.
astro128 said:
Nexus Q Install?
Any chance this can be installed onto a Nexus Q - I would love to get my Q-Ball back up and running!
Click to expand...
Click to collapse
I don't own a Nexus Q myself, so I won't be able to do any testing. The Q is running a full Android system, right? If it is, the receiver app most likely requires a later API version, or the Q doesn't support some of the features the cast receiver app requires to function.

I'm casting from a LG G3 and the Google Play services is on version 6.1.74
How can I send you the logcat? Can you PM me your email address?

rkirmeier said:
I'm casting from a LG G3 and the Google Play services is on version 6.1.74
How can I send you the logcat? Can you PM me your email address?
Click to expand...
Click to collapse
You can attach the logcat to your post, or use something like pastie.org or pastebin.com

Log attached to this post.

rkirmeier said:
Log attached to this post.
Click to expand...
Click to collapse
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will

HomerSp said:
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
Click to expand...
Click to collapse
That is correct. I'll work on getting the log from my minix and tablet tonight as they both have the receiver installed and do the same thing.

HomerSp said:
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
Click to expand...
Click to collapse
Minix log attached...
Thanks!

rkirmeier said:
Minix log attached...
Thanks!
Click to expand...
Click to collapse
Okay, I know why it happens now, but not the reason unfortunately. Do you think that you would be able to get a new log when you restart the media shell service? You should be able to connect to the Minix through the local network using ADB Konnect (https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect). Simply run ADB Konnect on the device and start the connection, then from your computer run:
adb connect <ip>
adb logcat
From another terminal run:
adb shell am force-stop com.google.android.apps.mediashell
adb shell am startservice -n com.google.android.apps.mediashell/.MediaShellCastReceiverService
The problem is that the signature that is used for device authentication is empty for some reason, and your log doesn't say why (the signature is generated when the service is first started).

HomerSp said:
Okay, I know why it happens now, but not the reason unfortunately. Do you think that you would be able to get a new log when you restart the media shell service? You should be able to connect to the Minix through the local network using ADB Konnect (https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect). Simply run ADB Konnect on the device and start the connection, then from your computer run:
adb connect <ip>
adb logcat
From another terminal run:
adb shell am force-stop com.google.android.apps.mediashell
adb shell am startservice -n com.google.android.apps.mediashell/.MediaShellCastReceiverService
The problem is that the signature that is used for device authentication is empty for some reason, and your log doesn't say why (the signature is generated when the service is first started).
Click to expand...
Click to collapse
I'm mostly new to adb other then a dozen or so roots I have applied (by guide) so I'm not sure if I'm doing something wrong here or what. I can connect from both computers and on the device I enter logcat then replies with "- waiting for device -". I know I"m connected because if I try to connect again it says I'm already connected. From the other computer I get the same response for logcat and when I enter your other commands to stop/start the service I get "error: device offline"
Any ideas to work around these issues? I would really like to get you the logs as it seems to be a common issue.

rkirmeier said:
I'm mostly new to adb other then a dozen or so roots I have applied (by guide) so I'm not sure if I'm doing something wrong here or what. I can connect from both computers and on the device I enter logcat then replies with "- waiting for device -". I know I"m connected because if I try to connect again it says I'm already connected. From the other computer I get the same response for logcat and when I enter your other commands to stop/start the service I get "error: device offline"
Any ideas to work around these issues? I would really like to get you the logs as it seems to be a common issue.
Click to expand...
Click to collapse
Is USB debugging enabled on the Minix? Settings > Developer options > USB debugging should be ticked.

HomerSp said:
Is USB debugging enabled on the Minix? Settings > Developer options > USB debugging should be ticked.
Click to expand...
Click to collapse
I confirmed USB Debugging is enabled. Wouldn't this be required to even make the connection?

Simple explanation to fix ADB unauthorized device in 'M'

QUESTION: Can someone please explain in simple form how to fix the ADB unauthorized issue that has been present since the update to M? The option for removing any current rsa keys is gone from the developer settings. And when you plug your phone in to a new computer it used to pop up a notification that would let you accept the rsa key. None of this is working any more. I cant believe that it is not a bigger issue and I have spent a few hours over a few days looking for a solution so if I have missed it, I am sorry. I have read a few things that say that google has just removed the ability to use adb and one post even explaining that, what looked to me to be a prop file variable, needed to be changed from 0 to 1, or vise versa, but didnt explain where the variable was. I dont see anything that I am confident with in the build.prop. Thanks. Please explain so that anyone will be able to overcome this issue, or point to a link.

Are you talking about the option to "Revoke USB debugging authorisations" under Developer options? It's there, at least on my N6 running stock 6.0.1 MMB29V... And I just tried to ADB to my device and the popup for the authorisation came up on the phone, just as it should.
I think you have some other problem going on.

Are you running the latest adb/fastboot tools on your PC?

Article showing removal of ADB
stevemw said:
Are you running the latest adb/fastboot tools on your PC?
Click to expand...
Click to collapse
Yes I am, I always use the one directly from the 'platform-tools' directory in the SDK. Another thing is I have read multiple articles that actually state that Google has removed the adb functionality in marshmallow... I don't get it. I even went from stock G.E. to CM an its exact same problem. Not to mention now I am dealing bwith the fact that the nethunter kernel isn't compatible with the CM build for Nexus... What!? Anyone can enlighten me on that subject I would love to know that as well... LoL. Here is link to one of the ADB articles though.
Tekto-kodi.com/kodi-news/marshmallow-android-6-removes-adb/

I looked at your link and the links provided in that article. The only thing I can read from those is that the ability to run ADB from your phone, i.e. from the terminal emulator (not your PC) has been removed. Are you trying to run ADB from your phone or your PC (I was under the impression that you're using your PC, but I have to ask)?
As I stated before, ADB from my PC to my N6 works just fine with Marshmallow (6.0.1 MMB29V).
You say that you use ADB directly from "platform-tools", but you don't say if you've updated the tools from the SDK-manager.