Related
Hi!
I've put an app together (99% based on "Wireless Tether for Root Users") which allows tethering via USB. Clients need to support RNDIS - works fine with Microsoft Windows (tested with XP and 7) and Linux (OpenSuSE 11.1).
Zinx Verituse has ported the essential parts of the hero-kernel and cyanogen has introduced this feature in his latest rom. So, thanks Zinx for the patches and cyanogen for publishing on github.
Patches can be found here:
http://github.com/cyanogen/cm-kernel/commit/9fd56ebdb6aba91e9b17ddea490ec9b39a819112
http://github.com/cyanogen/cm-kernel/commit/1a57339f015c3bfa097cf1d3e82f3485a6652483
I've decided to create this app to give all rom-cooks the ability to use this feature without modifying system-services and/or system-apks.
What a cook needs to do: Patch your kernel and recompile - all other stuff is done by the app.
Download:
http://code.google.com/p/android-wired-tether/
Features:
* Tethering makes use of the mobile-data-connection (HSDPA/EDGE/GPRS) or WiFi-connection
* Uses correct domainname-servers - provided by your carrier or which are configured on the wifi-access-point you connect (even if the network changes => switch from 3g to wifi and vice versa)
* Allows to change the local-network (network/subnetmask)
Supported ROMs:
* CyanogenMod 4.2.3.1+
* Android Dev Phone 1
=> my kernel-update needs to be applied: http://code.google.com/p/android-wired-tether/downloads/list?q=Kernel
* ?
Have fun!
Harry
THX a lot for this app
sudo dhclient usb0 and there you go
Good work.
Alot of the hero roms were finally able to get wireless tethering for root working on, well, hero roms. i installed, but cant get it working. What patch should i use, im using Sense Hero1.3.3
Hi Harry,
I'm visiting from the CDMA Hero forum, in the hopes that you might have some pointers on how to get this to work on the rooted CDMA Hero?
When I looked at this project over at code.google.com, it seems like this requires 1.6, where the CDMA hero is running 1.5. Will this fact doom us to ever run wired tether at this point?
From what I can tell on my Hero, everything seems to run fine until after I allow root access for the app. It then gives me a FC when accessing the system settings (as it's the one referenced in the FC.)
Can I apply your kernel safely to my ROM? Thanks in advance for your help!!
doesnt seem to work with macs
kmartburrito said:
Hi Harry,
I'm visiting from the CDMA Hero forum, in the hopes that you might have some pointers on how to get this to work on the rooted CDMA Hero?
When I looked at this project over at code.google.com, it seems like this requires 1.6, where the CDMA hero is running 1.5. Will this fact doom us to ever run wired tether at this point?
From what I can tell on my Hero, everything seems to run fine until after I allow root access for the app. It then gives me a FC when accessing the system settings (as it's the one referenced in the FC.)
Can I apply your kernel safely to my ROM? Thanks in advance for your help!!
Click to expand...
Click to collapse
Did you try http://forum.xda-developers.com/showthread.php?t=443025?
I've been using the wired tether for the past week and have experienced some issues. Mainly, if the tether app isn't in the foreground, the process seems to randomly get restarted. This manifests as brief hiccups in internet access for the connected computer. Didn't experience this problem using WT4R (in bluetooth mode).
HW: Dream
App: wired-tether-1.0.apk
Kernel: adp 1.6 usbtether-r3
OS: Vista SP2
If I remember to, i'll post a log later tonight.
Could you please explain (or put in the first post) why use this while the current tether in Network Settings (CM4.2.x) works just fine?
Proxin said:
Could you please explain (or put in the first post) why use this while the current tether in Network Settings (CM4.2.x) works just fine?
Click to expand...
Click to collapse
If usb-tethering with cyanogenmod is working fine for you there is no reason why you should use this app. I've implemented just a few enhancements (using the correct domainname-servers, changing lan-config) - I don't know how cyanogen is doing this stuff (I don't use it).
The main-idea of this app was to bring usb-tethering to other roms (where system-settings can't be modified or roms which a pretty close to stock roms and heavily modified parts are not welcome). All you need for this is a modified kernel which can be easily done.
jashsu said:
I've been using the wired tether for the past week and have experienced some issues. Mainly, if the tether app isn't in the foreground, the process seems to randomly get restarted. This manifests as brief hiccups in internet access for the connected computer. Didn't experience this problem using WT4R (in bluetooth mode).
HW: Dream
App: wired-tether-1.0.apk
Kernel: adp 1.6 usbtether-r3
OS: Vista SP2
If I remember to, i'll post a log later tonight.
Click to expand...
Click to collapse
yes, please post your log.
harry_m said:
If usb-tethering with cyanogenmod is working fine for you there is no reason why you should use this app. I've implemented just a few enhancements (using the correct domainname-servers, changing lan-config) - I don't know how cyanogen is doing this stuff (I don't use it).
The main-idea of this app was to bring usb-tethering to other roms (where system-settings can't be modified or roms which a pretty close to stock roms and heavily modified parts are not welcome). All you need for this is a modified kernel which can be easily done.
Click to expand...
Click to collapse
Ah, it hadn't occurred to me that other roms might not yet have tethering.
Thanks for your contribution then!
Very good! Thank you!
Anyone have the usb drivers for Windows XP?
Thanks in advance!
Has anyone used this successfully with Dwang 1.13? When Cyanogen came out with USB tethering it practically rendered mounting my sdcard and adb unusable. But this would be nice to use.
Sorry...Here's the link for it all.
http://bit.ly/wDDT0
awesome app
hey dude thanks for this app. i have cyanogenmod 4.2.5 and i know usb tethering is enabled on there but i didnt know how to get it to work. this app made it easy and painless i just had to download htc sync for hero and it worked like a charm. love it..
Just wanted to jump in and say thanks. I'm using this in my newest build and it works like a charm. I couldn't remember the authors name so i came here to get it so I can give credit, so while I'm here I wanted to say good job, and thank you
iflyabeech said:
Has anyone used this successfully with Dwang 1.13? When Cyanogen came out with USB tethering it practically rendered mounting my sdcard and adb unusable. But this would be nice to use.
Click to expand...
Click to collapse
i am also using dwangs v1.13 and am interested in the usb tether. i am a newb to all of this so if anyone has used these two together please let me know.
yaz813 said:
i am also using dwangs v1.13 and am interested in the usb tether. i am a newb to all of this so if anyone has used these two together please let me know.
Click to expand...
Click to collapse
This does work on dwangs 1.13 ... however it broke the cell network I was unable to get cell signal or network so it did me no good. I am working on way to fix this but I have not done dev for any phone in a long time, so it may take me a while to find out what is doing this.
youAdb is a very convenient tool for you android device which allows you to do various actions by just a couple of clicks.
Some features:
- SD-Partition-Manager (FAT32, EXT2/3/5, Linux Swap etc.!)
- App Manager (FULL BACKUP function!)
- File Manager (Push, Pull, Delete folders/files...)
- Reboot, Reboot Recovery, Adb Remount...
- View and automatically SAVE LOGS
- custom adb commands (like a shell)
- Install recovery images!
- Shows device's state and Serial Number
In contrast to most other android tools this tool is stable, leightweight (less than 1MB!) and easy to set up!
Watch a video tour: http://www.screentoaster.com/watch/stU0xUQ0VLQ1tZQl9UWVtf (ya, i know, my mic sucks.)
Screenshots:
DOWNLOAD: youadb.4shared.com
Nicely done.
It works great on my G1. I've not tested the partitioning section yet, but everything else works fine!
good job!
I keep getting ADB server is out of date
idbl_fanatic said:
I keep getting ADB server is out of date
Click to expand...
Click to collapse
..but you don't get this if you manually use adb via cmd?
try using sdk 1.6 and android 1.6
Works great on my G1.
A few suggestions:
Apps window, make the sections scalable because some app names are larger than the widow size.
Push/Pull window, allow double click to open the folder instad of having to go to enter to open it.
Reorder list by name
evilkorn said:
Apps window, make the sections scalable because some app names are larger than the widow size.
Click to expand...
Click to collapse
actually i'm reworking the whole gui right now to be fully scalable!
Push/Pull window, allow double click to open the folder instad of having to go to enter to open it.
Reorder list by name
Click to expand...
Click to collapse
ok i'm gonna do that too. good ideas.
fabsn said:
..but you don't get this if you manually use adb via cmd?
try using sdk 1.6 and android 1.6
Click to expand...
Click to collapse
I am such a noob for android, where would I get this?
Pretty cool, man. Good job on this!
idbl_fanatic said:
I am such a noob for android, where would I get this?
Click to expand...
Click to collapse
Get the sdk here:
http://developer.android.com/sdk/1.6_r1/index.html
(the adb file your looking for is in the tools directory)
i also recommend using the latest version of android (have a look at the development secion of the board) because i'm developing the software using a android 1.6 (donut) phone.
Pretty cool, man. Good job on this!
Click to expand...
Click to collapse
Thanks.
fabsn said:
Get the sdk here:
http://developer.android.com/sdk/1.6_r1/index.html
(the adb file your looking for is in the tools directory)
i also recommend using the latest version of android (have a look at the development secion of the board) because i'm developing the software using a android 1.6 (donut) phone.
Thanks.
Click to expand...
Click to collapse
My bad, I didn't have my phone in debugger mode.
New release. Build 01711.
Changelog:
-Scalable gui. you can adjust the fileviewers size to the size you want. very useful, especially if there are many long filenames.
as requested by evilkron.
get it here:
youadb.4shared.com
Nice changes
But one problem: The push/pull tab gets stuck and won't go back in folders after going a few folders deep and won't go back with the ...
I noticed that too. I'm gonna fix that right away...
---
fixed.
build 01711b
changelog: fixed filebrowser's "..." (go back) button.
download: youadb.4shared.com
Its working great on my G1, at least the first version, just dl'ed the new edition. Great job on this...keep up the awesome work.
Any feature requests?
I need something to work on
Question. I ran Google app backup.
Where does it backup too?
kizer said:
Where does it backup too?
Click to expand...
Click to collapse
I have no idea (i dont use it) and i dont understand how this question is connected with this thread.
great app clean and simple to use, keep up the great work
Joe333x said:
great app clean and simple to use
Click to expand...
Click to collapse
i really appreciate this comment as thats exactly what this app is supposed to be: fast, easy and functional.
there might be some other tools which have more functions (which i'm going to implement too) but they're not as fast and stable as mine is / will be!
NEW RELEASE: build 02111
changelog:
-push/pull file function updated
-MAJOR speed and stability improvements: app starts in less than 1sec and uses multitasking so that it will stay stable and is faster (especially when pushing files or searching fo .apks on ur computer!)
Download: youadb.4shared.com
________________________
NEW release: build 02211
changelog:
- added remount button
- slight ui changes
- fixed assemblyinformation
- improved "custom adb command" dialog
edit: fixed 1 more bug (you dont have to manually refresh the device stat to use the partitioning tool anymore)
=> build 02211b
Download: youadb.4shared.com
Status:
Working:
-Dialpad
-Bluetooth
-GPS
-Wifi
-Tattoo Buttons
-Touchscreen
-3g
-sensors
Not working:
-Fm Radio
-Camera
-Some Icns have wrong Size
-Some issues with graphics (mainly 3d)
Roms:
1) http://forum.xda-developers.com/showpost.php?p=5961430&postcount=50
Updated: 2) http://forum.xda-developers.com/showpost.php?p=6000675&postcount=103
better HTC-IME.apk http://forum.xda-developers.com/showpost.php?p=6089811&postcount=154
nexus launcher: http://forum.xda-developers.com/showpost.php?p=6100769&postcount=160
3) update 3 sensors working ) http://forum.xda-developers.com/showpost.php?p=6139158&postcount=197
4)V5 http://forum.xda-developers.com/showpost.php?p=6229047&postcount=300
thanx to : rhoa,ivendor,spartm and terminal 7
ps. sorry for the late update but I didn't have net connection.
ALL FROM THIS THREAD 5. april 2000 hours dk time
great ...reserved for future use
THX
Marsdroid
Is there any progress about porting android 2.1 to tattoo?
I have an OpenEclair port that works on Kaiser, with the edits to make the phone usable for QVGA. I'm sure there's a way to get OpenEclair working for Tattoo... the main problem I expect you'll face is enabling the new 3D drivers in the kernel.
can you please share it ?
I have an OpenEclair port that works on Kaiser, with the edits to make the phone usable for QVGA. I'm sure there's a way to get OpenEclair working for Tattoo... the main problem I expect you'll face is enabling the new 3D drivers in the kernel.
Click to expand...
Click to collapse
But tattoo doesn't have GPU :\
That's OK, 2.1 will run fast enough with only software rendering, we didn't have 3D working for a while. Having the 528Mhz proc (we only have 400Mhz) will help too. I will say that my build doesn't have SenseUI, 2.1 SenseUI doesn't work on QVGA yet AFAIK.
So we have to find the way to run 3d driver in the kernel and then we'll can use 2.1 rom? Awesome
No, if you don't have a GPU don't worry about 3D
Here's how I think you can do it:
Download OpenEclair 1.2.2 (http://openeclair.net)
replace the kernel with your kernel
(we use a different kernel for Kaiser and it works just fine)
Merge OE's build.sapphire.prop into OE's build.prop so Android uses the MSM7K drivers
(You can change in build.prop the 'sapphire' texts into 'tattoo', but it really doesn't matter)
Diff the init.rc's to check for differences and fix any important ones
(and you'll probably want to fix this minor bug in OE's init.rc)
Check the /system/ folder of OE 1.2.2, it might be too big for Tattoo's system partition. If it is, move some apps from /system/ into /data/app_s/ until /system/ is small enough.
Pack it up and flash it
The dialer doesn't fit perfectly on QVGA, but I have the .apks to fix that. First someone'll have to be brave enough to try to port a ROM and boot it
Me will do that later...
I'll be brave enough to test it. But I'm lacking the skills to try to port it myself.
Hi,
I've try this wrokarround, rewrite a updater-script, modify kernel for boot.img and init.rc.
But !!!! My device hang at "Tattoo" logo when he start, there is a solution for debug this step ?
I find
I used a boot.img from 5faif ROM and just change init.rc, not a good solution but device boot for this time
Now I have rom boot ok in 2.1 but screen resolution is bad ... next try maybe
--> you're my hero
If you manage to make a working 2.1 rom for the Tattoo you will become my new God ...
lgstoian said:
If you manage to make a working 2.1 rom for the Tattoo you will become my new God ...
Click to expand...
Click to collapse
I said the same
rhoa said:
I find
I used a boot.img from 5faif ROM and just change init.rc, not a good solution but device boot for this time
Now I have rom boot ok in 2.1 but screen resolution is bad ... next try maybe
Click to expand...
Click to collapse
Oh sorry, forgot to mention. In build.prop change:
Code:
ro.sf.lcd_density = 160
to
Code:
ro.sf.lcd_density = 120
That should fix it
I wish i could help in some way but i've only had my tattoo for an hour! Will love it if you guys get 2.1 working properly. Great stuff.
polyrhythmic said:
Oh sorry, forgot to mention. In build.prop change:
Code:
ro.sf.lcd_density = 160
to
Code:
ro.sf.lcd_density = 120
That should fix it
Click to expand...
Click to collapse
Uh.. plus you're going to need libs for audio/ gps and the ril for eclair. They're not the same as donut. Kaiser/vogue dev and tattoo dev are alot different.
you are the best
Liberation
"Free yourself from your carrier"
Features:
[ROM Base] HTC Droid Incredible 4.08.605.2
Android 2.3.4
De-bloated
Deodexed
Battery percentage
4-in-1 advanced power menu
Removed E911 location icon
Red scrollbar and overscroll glow to complement the Incredible's looks
Zip-aligned for optimal memory management
CDROM.ISO removed (prevents that annoying Verizon install prompt when connected via USB)
Uses edify script, will flash in Clockwork Recovery 2.x and 3.x.
Removed Apps:
Adobe Flash Player (install from Android Market if you want it)
Adobe Reader (install from Android Market if you want it)
Amazon MP3 (install from Android Market if you want it)
CityID (annoying 3rd party bloatware)
Facebook (install from Android Market if you want it)
Slacker Radio (install from Android Market if you want it)
QuickOffice (for those who want a free Office reader, try Documents to Go from the Android Market)
Verizon Bloatware (My Verizon, VCAST App Store, Verizon Navigator, Verizon Skype, Verizon Backup; most can be installed via Android Market)
Youtube (install from Android Market if you want it)
Downloads:
Liberation v3.0 - 143.08MB
MIRROR (provided by BrettApple)
Changelog:
v3.0 (January 6, 2012)
Based on the latest official RUU - 4.08.605.2 (Android 2.3.4)
Red scrollbar and overscroll glow to complement the Incredible's looks
v2.0 (September 20, 2011)
Based on the latest official RUU - 4.06.605.3 (Android 2.3.4)
System hardware information corrected in about phone (bug with official OTA)
Removed Sprint section/tile from Market, replaced with Verizon (bug with official OTA)
Only 688MB available to user (see explanation in FAQ)
No longer patched to block Android Market malware (Android 2.2.2 and above are immune by default)
v1.1 (June 25, 2011)
Added battery percentage meter.
More efficient compression (smaller file size)
v1.0 (May 19, 2011)
Initial Release based on November OTA (3.21.605.1)
FAQ:Q: What was the difference between the standard and enhanced versions of Liberation?
A: In simple terms, Liberation Enhanced was deodexed, while the standard version was not. However, since the Gingerbread update, HTC has deodexed the /system/app folder, but has left framework odexed. I've decided to just deodex everything instead of having two separate versions with minimal differences in available storage, but vast differences in customization.
Q: Why is the Android Market outdated!?
A: If I insert the latest market, it won't update on its own, meaning more work for you. The version of the market I'm using is outdated, but auto updates. It will update in the background the first time that you run it, and should be updated within 2-5 minutes depending on your connection. You'll need to exit and re-launch the Market for the update to take effect.
Q: Some of my Google Apps (such as Gmail) are an old version, but don't show up on the Market as installed or needing an update. How do I fix this?
A: This is a bug or "feature" of the stock ROM, I'm not sure which. However, it as a very easy fix. Simply open Gmail from the Android Market. From there, scroll down to "Developer Info" and select "View Applications." This will display all of Google's apps in the market. Scroll down and update every app that shows as needing an update (they'll all display correctly from here). You may also want to disable automatic updates from here.
Q: Why isn't <insert app here> removed, I consider it to be bloat!
A: HTC did their best to put together an experience utilizing their Sense software. I left that intact as every user will get something out of it. Some use Friend Stream. Some use only Facebook/Twitter/Flickr. There is no perfect combination as every user wants something different. My goal was to present a stock experience without the carrier bloat. There are ways for you to remove unwanted apps yourself if you'd like.
Q: Why aren't there any screen shots?
A: It's a stock ROM. I've done nothing to differentiate this ROM in appearance from what your carrier/OEM ships.
How to customize Liberation BEFORE you flash:
Materials
Windows - 7-ZIP
Linux - nothing
Mac OS X - nothing (note, I have not done this on Mac OS X, so I cannot support this OS)
Steps
Download the above mentioned file(s) for Windows. You can use a different archive manager if you'd like, but my guide is based on using 7-ZIP.
On your desktop, create a folder named "Test." You can name it whatever you want, but I'll be referring to it as "Test" in this guide. If you are new at this, you need to follow the guide to the letter.
Find your downloaded ROM and extract it to the Test folder. The easiest way to do this on Windows is to open the ROM, highlight all of the folders/files (CTRL-A), copy (CTRL-C), then open the Test folder and paste (CTRL-V). Give it a minute to extract the contents.
Once you complete step three, modify the ROM to your hearts content (see details below). Once complete, proceed to step five.
Open the Test folder and highlight everything (CTRL-A). Right click and select "Add to Archive." This will open 7-ZIP's archive manager. On Linux or Mac OS X, just right-click (or equivalent) and select "Compress."
In the options menu that comes up, leave everything at default except the following. The filename should be Test.zip (change Test to whatever you want). Archive format should be zip. Compression level should be ultra. That's it.
Once done, you can copy this zip to your SD card and flash as normal. Keep in mind that I am not responsible for any changes that you made in this ROM, so make sure you Nandroid BEFORE you flash.
Specific Modifications (using the above instructions):
Ringtones - While the ROM is unzipped, open the test folder and look for /system/media/audio. Within this folder you'll see several more folders (Ringtones, Alarms, Notifications). Any should files you put here will show up in the system when you go to change your ringtone (or whatever corresponds to the folder). The benefits to this modification include; no storage space used up in internal, phone, or SD storage; ringtone works even if SD is USB mounted, no errors when the SD card corrupts or is in use. The ringtones (alarms/notifications) are stored in a partition that does NOT count towards your file storage
Replacement "stock" applications - If you use a differnent web browser (like Dolphin HD or Firefox), or a different SMS/MMS program (like Handcent or Chomp), then it is recommended that you remove the stock applications before flashing. This prevents conflicts, slowdown, memory usage, and the annoying popup where you have to constantly re-choose your default application. In these examples, you are looking for /system/app/browser.apk and mms.apk.
Add/Remove apps you don't want - Navigate to /system/app, and remove any APK files that you don't want. If you don't know what app it is, do NOT remove it
Modify Bootup Animation/Sound - Navigate to the /system/customize/resource/ folder. In there, you will see two files; VZW_bootanimation.zip an VZW_Droid.mp3. These files are the bootup animation and "Droid" noise. Simply delete the MP3 if you want a silent bootup. It really is that easy. Replace the ZIP File with another zipped animation (must give it the same name) to replace the animation with one of your own. NOTE: Make sure you verify compatibility. If unsure, don't do it.
Files needed for UOT Kitchen:
Download - framework-res.apk
Download - com.htc.resource.apk
Download - SystemUI.apk
The above files are needed for the UOT Kitchen. Ask questions in this thread if don't know how to use them. UOT Kitchen allows you to change visual elements of your phone's stock interface in a way that no launcher app ever could.
jaykresge, you gonna get anything going with this gingersense leak?
Why is this based off the November OTA? Use the new gingerbread leak!!
Sent from my ADR6300 using XDA App
josh0426 said:
jaykresge, you gonna get anything going with this gingersense leak?
Click to expand...
Click to collapse
I'll mess with it.
tjrocks91 said:
Why is this based off the November OTA? Use the new gingerbread leak!!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Need to have the stable release out before the test/beta releases
This seems like a cool idea. Looking forward to the download links.
Sent from my PC36100 using Tapatalk
I agree.
I would love to see a ROM of yours based off of the Gingerbread Leak.
Nothing Special is the fastest and most stable ROM out. Hands Down.
I use it as my Daily Driver in a business setting and its perfect.
rosser725 said:
This seems like a cool idea. Looking forward to the download links.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Liberation is uploading right now, should be available in a few minutes. Enhanced is still cooking, might be another 30 minutes or so. As for the "cool idea," this is actually just a renamed update to an existing ROM. See below.
tincbtrar said:
I agree.
I would love to see a ROM of yours based off of the Gingerbread Leak.
Nothing Special is the fastest and most stable ROM out. Hands Down.
I use it as my Daily Driver in a business setting and its perfect.
Click to expand...
Click to collapse
I'm cooking Liberation Enhanced right now, then I'll immediately start playing with the leak. We've seen a few developers upload flashable versions already. I can't commit that I'll release anything on this leak at this point. Let me play with it some and then I'll comment on it.
Both 1.0 ROMs are up based on the November OTA. Currently toying with the leak, will update.
Re-cooking then uploading the beta for 2.00 based on today's Gingerbread leak. Use at your own risk.
I agree with tincbtrar.
Liberation Enhanced v2.00 BETA, based on today's Gingerbread leak, is now up. Use at your own risk.
jaykresge said:
Liberation Enhanced v2.00 BETA, based on today's Gingerbread leak, is now up. Use at your own risk.
Click to expand...
Click to collapse
Downloading now, Thanks.
I'm liking some of the changes. Reboot time (after initial flash) is insanely fast. HTC Car Panel now works in both portrait/landscape, however, most other apps still don't. Feels smoother than 2.2 (and I just did clean flashes of all of my ROMs, it's definitely smoother).
Let me know what you think, but so far, feels good for a beta. I'll make it my daily driver for the next few days and see what happens.
Downloading the beta now. Already a few out there, but I know you put out good work, and it's the slimmest so far. Fingers crossed, already put the new radio on. This is great! Long live the Incredible!
Will definatly give this a try when I get home.
Only thing that stinks is the cool mods (Pulldown Toggles, EVO Camera, ETC) wont work with the beta correct? Those pulldown toggles are amazing for me (Flashlight, Bluetooth and Sounds - especially)
Once that gets sorted out Ill be using your beta. Until then maybe ill flash Liberation for fun.
Great work sir.
Is 2.0 deodexed?
Sent from my ADR6300 using XDA App
BrettApple said:
Downloading the beta now. Already a few out there, but I know you put out good work, and it's the slimmest so far. Fingers crossed, already put the new radio on. This is great! Long live the Incredible!
Click to expand...
Click to collapse
Just an FYI, it works fine with the existing radio. I won't be pushing users to update radio/hboot/etc. until the official release comes out.
tincbtrar said:
Will definatly give this a try when I get home.
Only thing that stinks is the cool mods (Pulldown Toggles, EVO Camera, ETC) wont work with the beta correct? Those pulldown toggles are amazing for me (Flashlight, Bluetooth and Sounds - especially)
Once that gets sorted out Ill be using your beta. Until then maybe ill flash Liberation for fun.
Great work sir.
Click to expand...
Click to collapse
I'm going to work on getting an Evo camera working for it. As for flashing Liberation, it's just Nothing Special under a new name (and the minor change of Car Home switched for Car Panel). All of the mods you used on NS will work here
cabjmb said:
Is 2.0 deodexed?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes.
OpenPDroid is an awesome mod developed and maintained by CollegeDev, FFU5y, Mateor, Pastime1971, Syvat and Wbedard that allows you to configure for each app separately exactly which permissions it should have and block or spoof everything else. Unfortunately, it can only be used if the core platform is integrated directly into the ROM. (For more details, see http://forum.xda-developers.com/showthread.php?t=2098156)
Since I have completed the integration anyway during my attempts to fix the HDMI rotation bug (without success so far, I'm afraid) and the current version of CM does not seem to contain any more critical bugs, I thought others might like to make use of my ROM as well.
I therefore hereby present: CM 10.1 with OpenPDroid integration. Besides the platform integration I made the following changes:
PDroid Manager app integration.
Standard CM Updates are disabled by default.
CM anonymous stats collection is disabled by default.
Google Analytics integration has been removed from the CM stats collection module.
Updates and anonymous stats collection can simply be enabled again using the menu. (Warning! Applying a normal CM update purges the OpenPDroid integration!)
I will try to at least provide updates to newer versions at critical update moments and will perhaps provide some more in between.
You'll need to have ClockworkMOD installed in order to flash this ROM.
Downloads:
11/07/13: Version based on CM 10.1.1 stable. Steps:
1. Flash the stable version of CM 10.1.1 (10/07/13) for our device.
2. Flash this OpenPDroid patch.
3. Install PDroid Manager either from the Play Store or using the APK attached to this post.
10/07/13: (based on source code 09/07)
10/07/13: https://mega.co.nz/#!uswGGQ6K!Wt9JAFDBElZQ2i74yNxMrkz3y7kO4U8-LWK2dLx_L8s
10/07/13: MD5: 99fc3769c9b2354a844ac1ac92504650
16/05/13: (build with standard CM kernel)
16/05/13: https://mega.co.nz/#!StIyQbzD!GfgNa3Seha74UnSahokwIzvcZ9UVqKaa2P38_LlxuMY
16/05/13: MD5: ad036e4035291bba901ad90826ab0abf
13/05/13: (general source code cleanup)
13/05/13: https://mega.co.nz/#!KoxixajK!Wn91VGj5ooOFYXs-Vt8QJDkU8Bo7VuR40_939hd3YMg
13/05/13: MD5: dffad528804bf830c4b225b0bfff5a76
09/05/13: (WerewolfJB kernel v003 new)
09/05/13: https://mega.co.nz/#!2txwmS4S!aR4bHG6BHMkoTPabi8Z0K0r4hPsUICmKO9ROaaIYOg0
09/05/13: MD5: 4a75829296a167a563ad78ffe26991de
05/05/13: (vibration,memory management)
05/05/13: https://mega.co.nz/#!bsQERDaS!RHB4rHhQsDf9XauyOpeMySAiDt1gtc8Y7gnsckdWOlo
05/05/13: MD5: e05017acf9e50affcba7379050514d63
01/05/13: (merged in the WerewolfJB kernel, fixed headphone button actions)
01/05/13: https://mega.co.nz/#!ig5hCJYY!eHM5vwER9zEEZJRk9_C6vCvclH14rDcKa9CyBcU9kTc
01/05/13: MD5: 3ababb1c0cda47874ed7d688de032638
28/04/13 (adjusted some device references for improved custom recovery compatibility)
28/04/13: https://mega.co.nz/#!71BgVLBY!PEcEHAYxpDZVZcQycpgGJ2QeJZZ0HbgVdjaBkiD72bg
28/04/13: MD5: 7f2616736dd78940e37d1e14ea47084f
24/04/13: (storage, power profiles)
24/04/13: https://mega.co.nz/#!j44XWBDb!UrmGEhCUcjbj8Q3WTj1EkDrImXJXwcNGvEMIHFm-TvE
24/04/13: MD5: 491a500c5bef958d7575a6ce62fae1aa
23/04/13: https://mega.co.nz/#!75IDhCAA!EpwDqHm6W6fG3mk0lNaC0XPWvlsJxi2TjEpjJPEuj6Q
23/04/13: MD5: 609c76958796f19fb04aee217c44ba98
PS. If anyone ever discovers the correct procedure for calling the proprietary nvidia tegra driver api, please let me know.
is the baseband wakelock solved in this rom?
Who can change the other network disk ，thx
xtribas said:
is the baseband wakelock solved in this rom?
Click to expand...
Click to collapse
The main additional problem that this ROM currently fixes compared to standard CM is that of blatant privacy violation.
Since the wakelock issue seems to be related to mobile data use, and I don't have a data subscription, experimentation with this would quickly rack up my phone bill. If someone comes up with a solution I'd be happy to patch it out though.
Hansey said:
Who can change the other network disk ，thx
Click to expand...
Click to collapse
I assume you're referring here to the swapping of disk names when using MTP. I actually only noticed this bug last night and it should be easy to fix. I plan to have it patched out in the next version.
Update 24/04/13 uploaded, involving official CM patches for MTP storage & power profile settings.
Is there a guide how to compile it my self?
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1994860
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
At the Cyanogenmod website there are instructions for compiling yourself. You can apply the OpenDroid patches using the link I included in the post. Make sure to synchronize the proprietary files with those provided by Cyanogenmod or some aspects will fail to work.
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
SimonTS said:
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
Click to expand...
Click to collapse
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Wenque said:
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Click to expand...
Click to collapse
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
SimonTS said:
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
Click to expand...
Click to collapse
Good idea. I'll probably just expand the model check in the update script for future uploads so it accepts both references.
Update 28/04/13 uploaded, for some improved custom recovery compatibility. As every update, it also contains all official CM patches.
All patches between this version and the last one are minor, so for people who have installed the previous version of the ROM there is no need to update to this one.
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
No-body?
I have tried ths both with Derek Gordon's gps.conf modification, and with my own one using just the UK NTP servers and no fancy settings.
If I reboot the phone and run GPS Status & Toolbox it takes between 3 and 5 minutes to get the first lock. This happens whether I do it immediately on reboot or leave the phone alone for an hour first. Once it has established a first good lock, GPS seems to be very good - relocks quickly and stays in the background happily.
The problem is the first lock - it's almost as if the hardware is actually starting off disabled and takes time to warm up or something.
Can someone else using this ROM please test to confirm? I will try this with the standard CM 10.1 build and also with the Stock ROM again, but can't do so for a couple of days.
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Wenque said:
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Click to expand...
Click to collapse
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
SimonTS said:
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
Click to expand...
Click to collapse
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Wenque said:
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Click to expand...
Click to collapse
It's not that simple mate, but thanks for the reply. I know all about the gps.conf file as we used to have real problems with GPS on my old Desire S. The problem I see with this build and the standard CM is almost as if it doesn't know how to talk to the GPS hardware properly.
With the WerewolfJB build and my own gps.conf file I can get a lock in under 10 seconds sometimes, and always under 20.