Database Info

Android Wired Tether is patched and working for Evo

This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch

Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21

Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.

O Whoa, Wired Tether works on my stock Eris now Thank You

Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.

jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\

jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it

Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.

Thanks duder, works like a charm...
Sent from my phone.

THANKS!!!!

Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.

dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.

I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App

striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.

XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.

I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.

Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E

Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.

Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO

superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.

[Q] automatic reboot after lock up ALWAYS

Hello.
I´m new owner of Xoom "refurbished by motorola" bought on Don´tRetail.
With serie rom, updated by OTA to 3.2, all run perfectly. Enough smooth and run, but Quadrant give me a poor results (1700 points).
After unlock, flash recovery clothwork (3.2.0.0 rc4), I flash tiamat roms (2.0, updated 2.01, and later 2.1 hammerhead).
In all this scenaries, when just flash the new rom, work correctly, but when I installa any application...oh oh...
...when I press power button to suspend it, after eight second Xoom automatic reboot.
I back to stock status (reflash serie rom, serie recovery...all serie) and xoom work correctly.
when I reflash to use another time Tiamat´s rom...here is the problem...when I installed any application, if I suspend Xoom reboot automatically after eight second.
If I plug xoom to pc, and in "cmd terminal" I made:
adb logcat
I can suspend xoom without it reboot.
I tried to elevate minimal frecuencyes in setcpu, but same results.
I tried to do a logcat > logcat.txt in terminal emulator, and suspend the xoom...same result...reboot after eight second.
Any sygestions for I can use Tiamat roms???? With stock rom I have 1700 point in quadrant...with Tiamat without overclock (my xoom don´t let me overclock ) I have 2800 points.
A lot of thanks....Im so frustrated

Ok, I am just asking this to make sure I am 100% clear with this story.
Everytime you do an image with no apps and you shut down, the Xoom doesn't restart, but when you download applications it does... If this is so, I would suggest that you list the applications that you put on your tablet when it does restart, because to me, it sounds like it is an application that is bugging out on the Xoom.
Android systems are set up to force a restart if there are too many system resources being chewed up by applications that are a "High Priority" status and this causes a system resource lock up, and unfortunately, the only way to fix that is to force restart the system. IF it is a app that is doing it, all you need to do is make sure that app is not running to allow it to do so. Good ways of finding out is to use Titanium Backup (Marketplace) to freeze the apps (but that is only for a paid version...) or as someone else just previously suggested in another forum post is Autorun Manager where it allows you to freeze applications from starting up.
I would also suggest that you use the LogCat function in the SDK Tools that is stored in DDMS (aka ddms.bat located in the SDK TOOLS Section). This little program will allow you to do LogCat on your computer as well as save the log as a txt to upload to us (or for easy copy and paste) and as well as allows you to take screen shots and so forth. This might help you out finding the problem too as well as help us
So could you please give us these details to help you out even more?
Is this a Wi-fi only or 3g model that you bought?
Current Rom and Kernel (if I am wrong on the next two posts)
~Guess on Rom is: 2.1 hammerhead
~Guess on Kernal is: (I did not see where you said what the current Kernel was...)
Current Application List that Forces the Xoom to kill itself and reboot, even if it is just one... it might allow us to help you obtain a compatibility issue (if others are having the trouble with the same applications)
You had this trouble after you flashed the new ROMs, are the correct version? (aka Wi-fi only vs 3g romsm, cause there are 3g roms for Tiamat)
Did you clear the cache before and/or after you put the new ROMs on?
I hope we can get this resolved as soon as possible for you!
(links)
to get DDMS if you do not have it yet, please go here -- http://developer.android.com/sdk/index.html -- and you will be able to get step by step walk through to get the SDK. You will need to launch in Terminal/Command Prompt (depending on the Computer Operating System that you use.)

Firts...a lot of thanks for your answer.
With original-stock rom all work all right. My machines arrived with 3.1 Honeycomb, and via OTA updated to 3.2 (HTJ85B).
With this roms, all work correctly. I installed a lot aplications and work allright. I root this rom, and all are working well.
If I try to install any rom from Tiamat, doing previous wipe, the rom runs perfect. I install Titanium to reinstall all my aplications, and all work well. I can work about hours without problems...but with this roms (with all tiamat´s kernel and launpad kernel...) in the moment I suspend, after 8 or 9 second the tablet reboot automatically.
I tried to do a clean install, and only install one aplication, like flash player...and all are ok. After it, install another one, and after it another...but at tirth or fourth there is the problem another time...and tried with diferent aplications. Sometimes the problem go after install flasplayer, sometimes after install RepliGo, sometimes after install dolphinHd...
The more stranger thing is that if a plug the tablet to pc, and make a "adb logcat"...if I suspend de tablet...no problem, no reboot.
It´s possible that mi gpu aren´t righ? I say this because I guess that when the system go suspend, the gpu frecuencies go down (or gpu voltajes) and this made machine reboot... and it´s possible with tiamat´s kernel voltajes and/or frecuencies GPU are diferent than in stock rom.
It´s possible flash a tiamat rom without customiced kernel??? If I could try a tiamat with stock kernel, or with gpu without variation in voltajes or frecuencies.
NOTE: sorry for my english

So could you please give us these details to help you out even more?
Is this a Wi-fi only or 3g model that you bought?
Current Rom and Kernel (if I am wrong on the next two posts)
~Guess on Rom is: 2.1 hammerhead
~Guess on Kernal is: (I did not see where you said what the current Kernel was...)
Current Application List that Forces the Xoom to kill itself and reboot, even if it is just one... it might allow us to help you obtain a compatibility issue (if others are having the trouble with the same applications)
You had this trouble after you flashed the new ROMs, are the correct version? (aka Wi-fi only vs 3g romsm, cause there are 3g roms for Tiamat)
Did you clear the cache before and/or after you put the new ROMs on?
Click to expand...
Click to collapse
Some of my normal aplications:
Beautiful widgets
RepliGo
Documento2go
EzPdf
Titan¡um Backup
SeriesAndroid
Dolphin
Quick Boot
EsTaskManager
Astro, EsFilexplorer, rootexplorer, file manager
Aptoide
Pulse
I tried a lot combinations: for example with or without wifi, changing wifi suspend policy, with or withou configure gmail counts...with or without lock screen...
My Xoom are only WIFI 32gb (MZ604).

anfederin said:
Some of my normal aplications:
Beautiful widgets
RepliGo
Documento2go
EzPdf
Titan¡um Backup
SeriesAndroid
Dolphin
Quick Boot
EsTaskManager
Astro, EsFilexplorer, rootexplorer, file manager
Aptoide
Pulse
I tried a lot combinations: for example with or without wifi, changing wifi suspend policy, with or withou configure gmail counts...with or without lock screen...
My Xoom are only WIFI 32gb (MZ604).
Click to expand...
Click to collapse
I would actually ask if you have your wifi set to go off when the screen is off. This is a known issue...unless the wifi sleep policy is set to Never, the Xoom may reboot when the screen is off. It could be as simple as that.

Oh oh...so many probes that I don´t Know if I change wifi policy or not
But I remember dont change this between flash and install all apks.
At this weekend I´ll probe it and say you, now I need stable tablet to work.
A lot of thanks.

anfederin said:
Oh oh...so many probes that I don´t Know if I change wifi policy or not
But I remember dont change this between flash and install all apks.
At this weekend I´ll probe it and say you, now I need stable tablet to work.
A lot of thanks.
Click to expand...
Click to collapse
You can set it under wifi in Settings--->Networks...
Good luck!

[AOSP][ROM][4.2] Android JellyBean 4.2 PREVIEW

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of Android JellyBean 4.2 from AOSP source code based on the CyaogenMod device tree for Acer A700. I have made this build to gauge how difficult it would be to port JellyBean 4.2 to current devices.
Kernel Source Code: https://github.com/pawitp/android_kernel_acer_t30/tree/jellybean-next
Device Tree: None yet available (Only notable part: patch for TinyHAL: https://gist.github.com/4104332)
Downloads
ROM: http://goo.im/devs/pawitp/a700/a700_aosp_jb42_20121116.zip
Google Apps: Currently integrated due to lack of gapps package for 4.2
SuperSU: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip (Currently, only SuperSU is compatible with 4.2)
Installation
Note: due to new /data/media layout in 4.2 for multiple user support, your data in /data/media (/sdcard) will be moved to /data/media/0. This may cause problems in restoring backups in recovery, you may fix it by moving data /data/media/0 back to /data/media via adb in recover prior to restoring data.
Install CWM recovery from http://forum.xda-developers.com/showthread.php?t=1791165
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Wipe data if coming from stock
Known Issues
Camera does not work
Bluetooth sometimes freezes bringing down Wi-Fi with it
Reporting Bugs
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. The development of this preview will also cease once enough progress has been made in CyanogenMod.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.

gonna grab this later

Wow! This ROM is awesome. Please make it more stable. And the Performance is not so good as other ROMs.
Webitu

Webitu said:
Wow! This ROM is awesome. Please make it more stable. And the Performance is not so good as other ROMs.
Webitu
Click to expand...
Click to collapse
For stability: Please report crashes as mentioned in the OP, without logs, there'd be no way to know what broke.
For performance: Please report where and how performance differs.
Note that generic "please make this better" report do not help, please be more specific.

Runs so far, unfortunately I can not get a wifi connection. 'm Back to 4.1 back.

Fooox1 said:
Runs so far, unfortunately I can not get a wifi connection. 'm Back to 4.1 back.
Click to expand...
Click to collapse
Next time, please get a logcat.

pawitp said:
For stability: Please report crashes as mentioned in the OP, without logs, there'd be no way to know what broke.
For performance: Please report where and how performance differs.
Note that generic "please make this better" report do not help, please be more specific.
Click to expand...
Click to collapse
Okay sorry. The launcher laggs sometimes and the Antutu benchmark results are not really good.
The GPU test results are 967 points. (3D = 674, 2D = 293)
The fps are 31. In the stock ROM i had 42 fps i think.
And i havn´t any crashes but it seems like its a little bit unstable but it can be also the apps who are not official for 4.2
But very good work! :good:
Sorry for my bad English.
Webitu

The graphic issue can't really be helped, Android 4.2 requires new graphic drivers and the current binaries used are optimized for the Nexus 7. As there are closed-source binaries, there is no way to modify them. The situation may change in the future as compatibility layers are introduced or new drivers are released.

pawitp said:
The graphic issue can't really be helped, Android 4.2 requires new graphic drivers and the current binaries used are optimized for the Nexus 7. As there are closed-source binaries, there is no way to modify them. The situation may change in the future as compatibility layers are introduced or new drivers are released.
Click to expand...
Click to collapse
Okay thank you. I already thought so. Hopely Acer brings a new Update with 4.2
Webitu

Nvidia is the same xxx as samsung (

Is A701 supported?

It will work on A701, but 3G will not work.
BTW, CM10.1 preview. Nearly everything working (including Camera, etc.). Nightlies should start soon and I'll make a new thread then.
http://goo.im/devs/pawitp/a700/cm-10.1-20121216-UNOFFICIAL-a700.zip

pawitp said:
It will work on A701, but 3G will not work.
BTW, CM10.1 preview. Nearly everything working (including Camera, etc.). Nightlies should start soon and I'll make a new thread then.
http://goo.im/devs/pawitp/a700/cm-10.1-20121216-UNOFFICIAL-a700.zip
Click to expand...
Click to collapse
Yeah. Big thanks for your work! I will try it out now. Did you recognized that when you set a wallpaper on CM10 only half of the wallpaper is used on the homescreen? Don`t know how to log this issue.

OCmylife said:
Yeah. Big thanks for your work! I will try it out now. Did you recognized that when you set a wallpaper on CM10 only half of the wallpaper is used on the homescreen? Don`t know how to log this issue.
Click to expand...
Click to collapse
It's due to our screen size and peculiar wallpaper handling, so the default wallpapers don't scale too well.

pawitp said:
It's due to our screen size and peculiar wallpaper handling, so the default wallpapers don't scale too well.
Click to expand...
Click to collapse
Yeah I`ve tried logcat in the terminal, before I read your command. It shows no error-message when I changed the wallpaper. But I think I could live with this one.
I`ve encountered one minor Issue. You could change the default page size in the trebutchet settings, but it doesn`t take effect on your pages on the homescreen. Yeah really minor issue, but otherwise I haven`t found a bug so far. But I will search further.
Again. CM 10.1 looks absolutely awesome on the Acer A700 and I would recommend everybody who has CWM on his A700 to try this one out. :highfive:
Has anyone tried twrp recovery on the A700? I`m frightened every time to flash on my A700, cause I experienced the freeze issue also(one time so far, after I switched from CM10 to Iconian 2.2).

Trying to install CM10.1 but until now only bootscreen for 20 mins :/
Edit: hmm almost 40 minutes -.-
Tried Wiping Data/System/Cache now, but still Bootscreen loading and loading..

Chris0706 said:
Trying to install CM10.1 but until now only bootscreen for 20 mins :/
Edit: hmm almost 40 minutes -.-
Tried Wiping Data/System/Cache now, but still Bootscreen loading and loading..
Click to expand...
Click to collapse
Use adb to get a logcat, it'll tell you what's wrong. Normally, it's caused by not wiping data when coming from a stock ROM, but since you've said that you've wiped data, maybe there's some other cause.

pawitp said:
Use adb to get a logcat, it'll tell you what's wrong. Normally, it's caused by not wiping data when coming from a stock ROM, but since you've said that you've wiped data, maybe there's some other cause.
Click to expand...
Click to collapse
Which command parameters should i use ? Its a load of text.
If i want to save the log in a file with the -f parameter i always get the error, that the output file couldnt be openend and that my filesystem is read-only ..

Chris0706 said:
Which command parameters should i use ? Its a load of text.
If i want to save the log in a file with the -f parameter i always get the error, that the output file couldnt be openend and that my filesystem is read-only ..
Click to expand...
Click to collapse
adb logcat > log.txt
Sent from my GT-I9000 using xda app-developers app

So now i got the logcat attached, hopefully you find the error..

[ROM][7.1.2] LineageOS for microG [6/17/18]

Code:
I am not responsible for anything that happens as a result of you using the ROM. Sure, i'm willing to help with bugs, but if you get fired because the Alarm app crashed, gremlins crawl out of your arse, thermonuclear war starts, or if your progress in Clash of Clans gets reset, i'm not the one to blame.
Features
Code:
microG and F-Droid pre-installed
Anything else LineageOS can do
Is not certified cancer-free in California
Stuff you need to actually use this
- Unlocked Bootloader (duh). Seriously, I will ignore you if you mention that you tried to boot this with Safestrap.
- Update TWRP to Android-7.1 builds located here. Please make sure to use the recovery image which is appropriate for your device (Thor or Apollo)
How do I actually install this?
- Backup existing ROM if you want. Or don't. I don't really care, truth be told.
- Wipe /data partition. You can keep media storage if you want, but I prefer to format it to make it SQUEAKY CLEAN
- Flash the .zip
- Do not flash OpenGapps. Or any Gapps. That defeats the purpose of microG.
- Flash any other crap you want. This'll probably Magisk.
- Reboot.
Downloads
AndroidFileHost: Thor, Apollo
Extra junk you might want
Magisk
Yalp Store (play store wrapper)
Flashable Standalone Google Play Store
Sources
I didn't make any of this. I just compiled and signed it. People smarter than me, like hashcode and ggow did, made this work on the HDX. Lots of other people made LineageOS and microG. Thanks to you all.
Phoenix Kernel
HDX-Common device tree
Thor device tree
Apollo device tree
Docker instance that I use to build this
How do I tell the NSA didn't tamper with my download?!
Luckily, I signed the builds with my own key!
Code:
$ keytool -list -printcert -jarfile lineage-14.1-20180613-UNOFFICIAL-thor.zip
Signature:
Owner: [email protected], CN=steamport, OU=steamport, O=steamport, C=US
Issuer: [email protected], CN=steamport, OU=steamport, O=steamport, C=US
Serial number: b1b3cdcf593b5030
Valid from: Tue Jun 12 20:49:48 EDT 2018 until: Sat Oct 28 20:49:48 EDT 2045
Certificate fingerprints:
MD5: 13:E0:38:54:47:CC:FA:B8:24:50:16:6D:41:90:C7:4F
SHA1: 5F:AD:C9:4B:43:D3:1E:C3:6B:5F:86:DE:6A:F6:C7:F8:72:CB:B7:04
SHA256: BB:A1:BB:0F:7B:E1:62:2D:87:27:FE:EC:C5:CA:C6:B7:E3:EA:1A:CB:32:33:7E:F4:2C:D6:BC:BC:6E:46:27:CC
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
XDA:DevDB Information
LineageOS for microG, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
steamport
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader, TWRP
Based On: LineageOS
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-22

so confuse about microg. there are some games we must live with google play or the games can't run.
but micro g are great for user who not play games rely on google play.

locolyric said:
so confuse about microg. there are some games we must live with google play or the games can't run.
but micro g are great for user who not play games rely on google play.
Click to expand...
Click to collapse
What is there to be confused about? Yes, Google Play Games doesn't work with microG yet. Just don't play with games that mine your data. Problem solved. Or just try to lubricate it with cat piss. I don't care.

Stupid Question: does this support LTE?

CCF_100 said:
Stupid Question: does this support LTE?
Click to expand...
Click to collapse
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.

CCF_100 said:
Stupid Question: does this support LTE?
Click to expand...
Click to collapse
steamport said:
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.
Click to expand...
Click to collapse
Correct - only KitKat based custom ROMs support LTE (data only). FireOS 4.5.x is the best choice for voice and mobile data support.

New zips are out. I just updated microG's GMSCore to one I built myself based on master and a fix PR. Also pulled from latest Lineage 14.1 sources.

Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..

NeverSmile said:
Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..
Click to expand...
Click to collapse
Likely won't be any different with this ROM as core issue resides at the kernel level. Inconsistent connection behavior leads to erroneous claims based on individual experiences but really not ROM related other than the binary KitKat (Android 4.4.x) or above checkpoint.

Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again
Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.

kfhdxuser said:
Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again
Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.
Click to expand...
Click to collapse
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:
Code:
adb shell
logcat > log.txt
exit
adb pull log.txt
, then put the log.txt on pastebin and give me the link

Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can.

kfhdxuser said:
Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can.
Click to expand...
Click to collapse
I've seen the dialog pop up as soon as it finishes booting

Done!
steamport said:
I've seen the dialog pop up as soon as it finishes booting
Click to expand...
Click to collapse
Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).
I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur

kfhdxuser said:
Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).
I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur
Click to expand...
Click to collapse
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?

steamport said:
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?
Click to expand...
Click to collapse
Yep i'll do that, was it the method that I used to extract the log file that could be the culprit? I should probably mention that you can see the screen when it turns off and on its just a different shade of black indicating that the screen works but it just won't display anything if that makes sense. I'll do a complete wipe and start again to see if its any different this time around.
Edit: Here is the new log: https://paste.ee/p/VK4oS
^^^
I've noticed it is considerably smaller this time around so hopefully this a good sign haha.
It is weird how the previous release worked and this one doesn't, i'd assume it's an application interfering from the latest build but if it works on Thor then it mustn't be right? Maybe something was accidentally changed for the Apollo release somewhere. Sorry if my ramblings aren't useful

Thanks @steamport! What is the security patch level on this build?

NextDroid said:
Thanks @steamport! What is the security patch level on this build?
Click to expand...
Click to collapse
Whatever the latest for 14.1 was as of 6/7/18?

steamport said:
Whatever the latest for 14.1 was as of 6/7/18?
Click to expand...
Click to collapse
Well, that depends, as the last AEX build, for example, was still on May 5.
Tapatalk を使用して私の LG-RS988 から送信

steamport said:
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:
Code:
adb shell
logcat > log.txt
exit
adb pull log.txt
, then put the log.txt on pastebin and give me the link
Click to expand...
Click to collapse
I've got the same problem. Loads but no screen and unable to find the "ok" to authorize the device. There must be a better way.
I will revert back to previous version until this is fixed.

Is it possible to root the "Nokia 8110 4G" running KaiOS ?

Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB

sgmarouf said:
Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB
Click to expand...
Click to collapse
Im also wondering the same thing

Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.

nexus511 said:
Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.
Click to expand...
Click to collapse
Good job! :good:

0312birdzhang said:
Good job! :good:
Click to expand...
Click to collapse
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.

nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
This is a good news! I just bought a "banana" today, waiting for your good news :fingers-crossed:

nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
Sounds like you've made some impressive progress here, can't wait for more details!
Will you be posting a more detailed tutorial/how-to here or on your blog in the future?
Keep up the great work! :good:

Great work, would be great to uninstalled preinstalled *tty demo games.

@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse

fpb4 said:
@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
Click to expand...
Click to collapse
Use OmniJB can enable "Developer Mode".
Tested on sideload mode

0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?

0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Is there anyway I could revert installing omniJB? I'd love to be able to install factory updates again.

hello all, just give an update on how's everything regarding nokia 8110 is going

fpb4 said:
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?
Click to expand...
Click to collapse
Could you remove the pre-installed apps?

Hi!
It's possible, to get full ADB-Root by injecting a patched adbd-binary. And with real swap instead of zram, the device is more responsive (background-tasks like Launcher/Homescreen are killed less often...)
As soon, as I have build my own patched adbd, I will provide an 'update.zip' -- it seems chainfire doens't like others to use his version. (OpenSource -- anyone? )
BTW: no, I don't have 'su' -- only my own priviledged additional startscript and ADB-Root but for me this is more than enough to 'work'
(my goal is to create native apps with Ada/Gnoga - meaning native but with HTML5-GUI. First tests are working well...)

I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?

It should be possible to remove those apps - but for me it's hard to say how. On my device there were no preinstalled apps/games other than snake. Everything else is (un)installable normally. Could be a region-thing
(I've got the european/german version)
-- but on my device the store seems to be a 'static' bunch of zips - so it could kill the store to just remove those.
(i think I would need to adjust configs for the store if I want to clean them up)
If I remember correctly, there is a flag in the app-manifest to config if an app is removeable... my first try would be to edit this flag and check if I could uninstall it normally after this
On the other hand: there is nearly no need to uninstall - KaiOS-Apps are small and with a sdcard....
(I created an extra 1GB-Swap on /data - even then enough space left)
BTW: if You have a little experience with android-stuff, rooting is simple when You know how
Enable adb --> just type *#*#33284#*#* on keypad of your phone (the digits spell 'debug' )
-- build an update.zip - sign with AOSP-Test-Keys
--- let it create '/data/opt', '/data/opt/bin'
--- put an patched adbd (chainfire's v22 works) in /data/opt/bin
--- create /data/opt/init as a shellscript, remounting / rw, replace /sbin/adbd with patched one, remount / ro kill adbd so it restarts the patched version. (you may add commands for other stuff on boot - I disable zram, enable swapfile, start en Ada-Server....)
--- and add a call to '/data/opt/init' as last line to '/etc/init.qcom.post_boot.sh' so this 'init' will start with root-rights on startup.
This way /data/opt/init will inherit root from /etc/init.qcom.post_boot.sh, so it can replace adbd - and because the patched version won't drop it's root-rights you'll have a root shell over adb.
As You see - it's quite trivial, but at the moment I don't have a patched adbd which I'm allowed to include.
(I hadn't time to build an AOSP-tree until now)

Has anyone tried installing OmniJB from 4pda.ru website? (Sorry can't post links)
If you google "4pda 890710" it will bring it up.
Also, anyway of installing whatsapp yet?

PolePolisher said:
I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?
Click to expand...
Click to collapse
root or create an update to edit /data/local/webapps/webapps.json
it worked on my phone no more s*** games and google stuff

Can I not just replace the /sbin/adbd from the boot.img?
(by extracting the boot.img with a flashable zip, and then unpack/repack with kitchen)