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.
Related
I take no credit for this, just passing information on for others to use. YMMV, use at your own risk..
roebeet pointed this out in irc;
SOURCE: http://notioninkhacks.com/forums/viewtopic.php?f=29&t=891
by StephenH » Wed Feb 16, 2011 1:58 pm
ok folks im hoping people can test this for me,
just built a new build (my first for the adam) based on the newest official 2.2 build but with some interesting tweaks
NOTE: i am a dev working for NI especially on honeycomb soon, but these roms are my own.
changelog:
New Kernel with NTFS support, android does not mount this by default but you can mount it via adb read only. (kernel has rw support but i couldnt get it to mount a ext drive rw)
Kernel has few other tweaks and changes and doesn seem to die when sleeping either now
performance tweaks (minor ones) made to the os itself
full google apps added (untested )
ability to disable ril/phone features to conserve battery (see below for info)
adhoc wifi courtesy of the update posted on this site previously
disabled some of the logspam that was enabled but isnt needed
boot.img is first stage prepped for honeycomb
install instructions
download the file linked below and copy to either sd or your adams internal memory and flash as normal
download:
Code:
Please refer to original post linked above for download link
RIL Disabling Information
ok this is a creative feature. all adams be them 3g or wifi only versions keep thje phone related applications and services running in the background and on the wifi only adams this causes a higher battery drain due to system constantly trying to connect to a network, i have implemented a way to disable this by setting a simple property in the system
to do this you need to edit the /system/build.prop file and change the mentioned line to 1 instead of 0 then reboot
if that doesn work then try the below route
open a terminal and run the following command then reboot
Code:
setprop persist.ril-off 1
Click to expand...
Click to collapse
I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App
football0552 said:
I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It is probably because there aren't very many Adam users yet.
keitht said:
It is probably because there aren't very many Adam users yet.
Click to expand...
Click to collapse
Yeah I think there are very very few adam owners out in the wild. Might be a decent bump after this next delivery round next week.
And NI has not officially released their kernel source and from my discussions with them I wouldn't expect it real soon. I did however explain to them that it will have to be eventually so I think they might be working on it.
rothnic said:
Yeah I think there are very very few adam owners out in the wild. Might be a decent bump after this next delivery round next week.
And NI has not officially released their kernel source and from my discussions with them I wouldn't expect it real soon. I did however explain to them that it will have to be eventually so I think they might be working on it.
Click to expand...
Click to collapse
They don't seem so keen on sharing huh? Interesting since they like to use other people's open source code...
Guess I will have to join in and start hounding them about it.
Sent from my ADR6300 using XDA App
keitht said:
It is probably because there aren't very many Adam users yet.
Click to expand...
Click to collapse
I second that. Am a fervent flasher (the right kind....) and when I get my Adam I will certainly be putting my own 2 cents in to get the most out of it, both OS and UI wise.
I am not alone, so definitely expect a flury of activity by Adam enthousiasts once the next 2 batches are delivered.
Sent from my HTC Desire using XDA App
You guys are lucky to have djsteve as your new Dev. He's put in a lot of work for the Dell Streak since it first came out and he will probably put in a lot of work for the Adam ink as well.
football0552 said:
I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my Dell Streak using XDA App
I get mine tommorrow so I'm very excited.. will def try this
sent from gv1.5 on g2
Update: 10/03/2011:
UPDATE: 10/03/2011:
time for another update
changelog:
reverted vold change as it screws up things
added some more perf tweaks,
added data2ext script from gtab forum on xda, seems to work nicely, can hit quadrant scores of ~3200 now
flash you will need to install yourself at moment, i forgot to readd it link for flash : http://forum.xda-developers.com/showpos ... stcount=26
Code:
refer to original thread/forum for download links
enjoy folks and if anyone wants to do another video feel free.
---------------
UPDATE: 17/02/2011:
ok have tweaked a bit more and made a few more changes.
changelog:
new vold added with ntfs mount support (see below for some issues known with this)
flash player added and should auto install
fixed market and facebook
fixed superuser ability
added estrongs file manger for root use
tweaked the ril scripts to be easier to use.
added modified nvrm_daemon to increase 2d framerate
Code:
refer to original thread/forum for download links
*note for VOLD, this now mounts ntfs drives read only, but it has slightly screwed up the mounts, if you power up device with no microsd plugged in it will mount the internal storage and allow access to is via usb, if you plug in a microsd or boot with one in it will mount both internal and external sds but share the external over usb, it quite happily detects and mounts my 1tb usb hdd which is ntfs formatted though now.
ril tweaks: now all you need to do is create a empty file on your memory card called riloff.txt then reboot and script should do the rest to reenable rename the file rilon.txt and reboot
enjoy folks and if anyone wants to do another video feel free.
-----------------------
ok folks im hoping people can test this for me,
just built a new build (my first for the adam) based on the newest official 2.2 build but with some interesting tweaks
NOTE: i am a dev working for NI especially on honeycomb soon, but these roms are my own.
changelog:
New Kernel with NTFS support, android does not mount this by default but you can mount it via adb read only. (kernel has rw support but i couldnt get it to mount a ext drive rw)
Kernel has few other tweaks and changes and doesn seem to die when sleeping either now
performance tweaks (minor ones) made to the os itself
full google apps added (untested )
ability to disable ril/phone features to conserve battery (see below for info)
adhoc wifi courtesy of the update posted on this site previously
disabled some of the logspam that was enabled but isnt needed
boot.img is first stage prepped for honeycomb
install instructions
download the file linked below and copy to either sd or your adams internal memory and flash as normal
Code:
refer to original thread/forum for download links
RIL Disabling Information
ok this is a creative feature. all adams be them 3g or wifi only versions keep thje phone related applications and services running in the background and on the wifi only adams this causes a higher battery drain due to system constantly trying to connect to a network, i have implemented a way to disable this by setting a simple property in the system
to do this you need to edit the /system/build.prop file and change the mentioned line to 1 instead of 0 then reboot
if that doesn work then try the below route
open a terminal and run the following command then reboot
Code:
setprop persist.ril-off 1
Last edited by StephenH on Thu Mar 10, 2011 6:15 pm, edited 2 times in total.
Click to expand...
Click to collapse
[UPDATE]2012-08-06 This is not the only way of getting Dongle's working on Android, If widgets are your thing and you doing feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android.
[UPDATE]2012-08-06 The source to libhuaweigeneric-ril ( github ) has been updated to include fixes made by omegaRed7 - This massively improves the fault tolerance upon RIL Startup, Tests were carried out on the E173s-1 but it should be beneficial to all modems ( I hope ).
[UPDATE]2012-07-28 As the Rom Version is quite old and it doesn't really require it's own rom I've extracted the files required to implement this functionality - Download Here, The Archive contains a README file with installation instructions
IMPORTANT - pppd permission need changing to 6755 also change to ownership to the root account ( Thanks to __DS__ ). you can do this through adb or terminal emulator
Code:
adb shell chown 0:0 /system/bin/pppd
adb shell chmod 6755 /system/bin/pppd
for this to function
[UPDATE]2012-06-25 Added Forked libhuaweigeneric-ril to Github Repo this includes all the changes I've made - Check This Post For Details
[UPDATE]2012-06-23 Added Github Repo - Check This Post For Details
[UPDATE]2012-06-16 THE DOWNLOAD LINK HAS BEEN UPDATED AS THE FILES IN /etc/system/usb_modeswitch WHERE NAMED INCORRECTLY[/UPDATE]
Hi Folks - This post is going to change fairly often, there is still more info to add, I just got bored with typing for now
The Sales Pitch
This rom aims to provides the same "hands free" approach offered by the Archos 3G Key and extends this functionality to Huawei Branded USB Modems.
Introduction
Here is a custom rom I've currently been hacking away at, if feels like I've had it under wraps for months.
That being the case. I'd like to thking on to enable Huawei USB Modems - This is still a WORK IN PROGRESS but It feels like i've been keeping it under wraps for months, So it's time to throw it out there for further testing. So Dongles at the Ready! It could get a little hacky
WARNING
The Full Size USB Slot has been known to fail from moderate use. As such I would recommend using an USB extensions cable for connecting devices.
VERY IMPORTANT NOTES - PLEASE READ
1. This is definitely not an every day use rom on any other device this woud have been deployed as a recovery flashable update. The reasoning behind the rom deployment is it's only one file to copy and youi're ready to go. It is also a tedious task to manually go through (especially on the 100th time
2. Please don't ask a me if a certain device will work or not. It is not helpful on a number of levels,
a) I simply don't know - I don't own the model in question. Further more you can figure it out yourself.
b) The Chances are that you could probably find out the answer without leaving the comfort of xda - The libhuaweigeneric-ril has been passed around xda like a <Insert Well Used Analogy Here> so a quick search of xda may turn up something useful to reassure you.
c) In reality though we are not going to know if your dongle is working until you "Try It Yourself".
3. if you find your device doesn't work then you need to gather all the relevant information to help get a feel of what's going on; See Below
SUPPORTED DEVICES
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
IMPORTANT NOTES - WHAT YOU NEED TO KNOW
In a perfect world you can download/flash the attached update file. Reload your SDE, Plug a USB 3G Dongle and have It connect and go about you day .
This is the ultimate goal and currently what happens on my own device
TROUBLESHOOTING
There's about a 25% based on my current test this won't happen. There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprops
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
Please have a glance over it before posting as It may contain information that you would not want others to see!
ROM DETAILS
Android Version: 4.0.3
Archos Version: SDE 4.06
Removed : Nothing
ADDITIONS
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
DOWNLOAD
3G Modem Redist Pack - For use with newer roms
Hotfile - archos.ext4.update.
INSTALL
Unpack zip and copy unpacked update file to the device
Code:
adb push archos.ext4.update /mnt/storage
restart device in sde mode
script should update automatically
KNOWN ISSUES
"3G Stick Connected" Icon remains in notification list after device disconnection.
pppd needs to be executed with elevated privileges.
pppd is not exiting correctly on some occasions and cause reconnection issues when using multiple sticks.
Thanks go to surdu_petru for the base sde, derAtem for his original work on the libhuaweigeneric-ril.so and pretty much every developer who has worked on these dongles with android, I think I've read every thread on XDA regarding this subject
Hi!
Thanks trevd!
I do not have this USB modem ....but you did a good job for those who have this modem ! Good luck...
i have a Huawei E160E
It is possible to add this modle on your rom ?
---------- Post added at 06:46 PM ---------- Previous post was at 06:23 PM ----------
For the buzz in FRANCE (and in the World :-= )
http://www.jbmm.fr/?p=28280
cajl said:
i have a Huawei E160E
It is possible to add this modle on your rom ?
Click to expand...
Click to collapse
Is this a new model ( released this year )? It may already be in there, The easiest thing to do is plug it in.
If you install this app you can find out what the product_id is and then we can find out for sure.
Thanks
no released in 2009
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 12d1
Vendor Name: Huawei Technologies Co., Ltd.
Product ID: 03eb
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Rackham666 said:
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Click to expand...
Click to collapse
Hi Rackham666
I'd refer back to my first post, I've tried to make it a little more clear what this "rom" exactly is, more a testing ground, my apologises if that wasn't very clear at first glance, So to switch this query right back at you.
After installing my rom, I'd like to know if your Huawei K3565 is supported?.
For my usn dongle , is it ok for you ?
Okay.
I'll try your additions manually when [email protected] V3 will be released by Petru.
Get The Code
Hi Folks.
I've started a github repo if anyone wants to hack on this stuff.... It only contains the code for the hotplug service at the moment but I will obviously add more when I get chance and apply all the proper GPL licenses to it.
A personal word of note : C is not my first language by any stretch ( although it is fast becoming the case ) so If It causes any memory leaks or starts nuclear war I can't be held responsible, however if there is any noob coding errors in there then I'm ready to learn off those more knowledgeable than I. I have a feeling we have some hardcore developers lurking in Archos Development community
Equally If anyone has any fixes drop me a pm and I'll sort commit access on the repo or post them right here in the thread,
The code can be found here https://github.com/trevd
Hi Folks, Me Again!
Just to let you guys know I've added a forked libhuaweigeneric-ril to my github ( https://github.com/trevd )
It includes the changes I made to enable it to work the Archos.
You'll want to clone the ics branch if you want to compile yourself.
cajl said:
For my usn dongle , is it ok for you ?
Click to expand...
Click to collapse
???
I'm not sure I understand what you mean.... can you explain a little more
Thanks
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
Hi Alahkel
You're not bothering me .... DO I really sound/come across as that grumpy/angry in my first post.... sometimes I get cranky when I don't get enough sleep.... too much time looking at code.... :laugh:
Thanks for having a go, Are you using the official SDE? and have you got a working SDE Rom already installed?
For now I would forget about the rom image and bear with me, I'm working on an installer APK which will probably better help with testing, I'll also put the manual installation method up for those who want to get dirty with adb.
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
trevd said:
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
Click to expand...
Click to collapse
Hi, thx for answering. Well of course I turn on the 3g key in settings for big-size usb and my huawei 3gkey is on indeed (led on key) but the tab doesn't recognize that o.o I'm on tim (italy ) Thank you
Sent from my ARCHOS 101G9 using xda premium
Hi trevd,
i'm guessing this won't work on CM9 by JackpotClavin, or would it? If yes, would i install it the same way as described?
Thanks in advance!
Edit: Sorry i'm obviously still running in 1st gear in the morning... There's no 3G support in the CM9 port so there's no way this would just "work"...
Edit2: And confirmation that i need more coffee: Saw your post in CM9 thread about the successful connection with Archos' 3G stick and a Huawei 3G stick, but only through the browser... Any progress on fixing things so the ppp connection is fully usable by other apps & services?
Hi, trevd!
how to launch the modem on a firmware 4.0.7?
I copy these files from your firmware
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
Click to expand...
Click to collapse
I change the init.rc file for init.dongle.rc start
but the Huawei E1550 modem doesn't work
what it is necessary to change still?
Thanks!
=========================
sorry, everything earned, it was necessary to update a modem firmware
Hi deman05
You were nearly there, init.dongle.rc is imported on the very first line of init.rc so you need both files.
You shouldn't have to do anything with the modem firmware as usb_modeswitch will handle turning the modem.
The files required are.
init.rc
init.dongle.rc
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
/system/bin/hotplugd
Also you need the full contents of the following directories
/system/etc/usb_modeswitch
/system/etc/ppp
/system/etc/chatscripts
I've attached the latest versions to this post (hopefully I've not missed anything), you will need to change the permissions on /system/bin/pppd.
chmod 6755 pppd
[EDIT] I did miss something, please see the first post for the correct download link.
The new version also handles a cold boot ( modem plugged in on startup ) scenario.
If you are still having issues please refer to the troubleshooting section in my original post
Thanks
===============================================================
Issue closed, read:
http://forum.xda-developers.com/showpost.php?p=42638124&postcount=17
===============================================================
l2_hsic issue
l2_hsic running amok (GT-P7500, GT-P7501) is ONE considerable reason for abnormal battery drain.
The so far known counter measures (HC, Stiffmeister + its xda derivate, WiFi-ROM) do not comply to my requests:
- CM10.1 nightlies
- 3G usage
- no l2_hsic hassle
l2_hsic root cause
Analysis of kmsg files provide a consistent pattern. Function if_usb_suspend(..) from modem_link_device_hsic.c does not call wake_lock_timeout(..) in wakelock.c in case of l2_hsic is running amok.
The missed call to wake_lock_timeout is obviously caused by a non cancellable USB-connection.
It is a single non expiring wakelock, what makes trouble.
Inside of modem_link_device_hsic.c I lost track on further explanations.
Candidate to fix the issue
Since I cannot correct the root cause, I tried to fix its consequence.
Basis is the current pershoot P4 CM10.1 kernel.
There are a few spots in its source code, where one could obtain the so called prevent_suspend_time of a l2_hsic wakelock.
A monitor is installed in such place. It triggers, when a l2_hsic wakelock’s individual prevent_suspend_time exceeds >10s (empirical value).
In this case the function wake_lock_timeout is called, which ignites the wakelock’s expiration.
Next the trigger is reset and the monitoring becomes active again.
As a second and measure of last resort the tab is shutdown, once l2_hsic’s total prevent_suspend_time exceeds >1h (never happened so far).
All these events are logged:
--> /proc/grzwolf shows current status
--> /proc/kmsg is extended by a couple of messages
Verification
The described modified kernel was installed on my Tab months ago.
Since then DS works perfect to me.
Furthermore I did not experience any side effects.
This kernel-mod had been announced at
http://www.android-hilfe.de/samsung...s-10-1n-mit-stock-4-0-4-a-69.html#post5550736
Meanwhile the kernelmod is integrated:
BeeGee(Ganbarou), AAccount(A1 Kernel), kasper_h(Team Infamous/AOKP) and twa_priv(CM10.1/SGT7)
Preconditions for installation
- the kernelmod applies only for P4 devices (GT-P7500, GT-P7501)
- no need to contiue, if you don’t have a l2_hsic issue
- if you continue, you should know what you are doing
- I don’t take any warranty
- after flashing a Nightly ROM, the kernelmod needs to be installed again
- CM10.1 is installed on P4 according to the OP of thread http://forum.xda-developers.com/showpost.php?p=36077123&postcount=1
Kernelmod installation
- comply to the preconditions above
- within CWM make a Nandroid backup of a running isntallation
- copy 'P4 kernel' (see downloads below) to your Tab
- install 'P4 kernel modified' within CWM and check functionality after booting up
- if not ok, restore in CWM your Nandroid backup
Credits
- pershoot (Kernel)
- MapleSyrup (Kernel build)
- nakedninja42 (CM10.1 Installation)
Changelog
Rev. 2013.04.10-19.44
first release
Downloads
- CWM flashable kernel zip, Rev. 2013.04.10-19.44
- md5 sum of kernel zip
- source code
- readme source code
All hail grzwolf! Thank you so freaking much for finally finding the fix that no one could. I now don't need to flash a WiFi ROM to get rid of the l2_hsic issue.
Sent from my GT-P7500 using XDA Premium HD app
Great work, grzwolf!
Did you find the root cause of the wakelock based on your extended logging?
Is it OK for you if I take your code, streamline it a bit (remove logging, renaming methods, ...) and integrate it in the CM kernel?
C-o-M said:
Great work, grzwolf!
Did you find the root cause of the wakelock based on your extended logging?
Is it OK for you if I take your code, streamline it a bit (remove logging, renaming methods, ...) and integrate it in the CM kernel?
Click to expand...
Click to collapse
Root Cause
According to my current testing (next revision kernelmod), I'm almost convinced it's caused by a race condition
between modem and modem interface (most likely the "kill_urb stuff").
Just by adding the extended logging in "if_usb_suspend" seem to have wiped the issue with the missing "wake_lock_timeout".
As next I'm going to switch back to the erroneous behaviour, verifying this theory.
If this approach would stand, the extended logging could be replaced by reasonable delays.
Not impossible, that the whole silly detection & triggering in wakelock.c is not needed.
Usage
That would be fine to me, so no problems at all with code re use.
You mean the issue is fixed by just adding some delays in if_usb_suspend? So you do not enter your wake lock fix at all with the current patch?
C-o-M said:
You mean the issue is fixed by just adding some delays in if_usb_suspend? So you do not enter your wake lock fix at all with the current patch?
Click to expand...
Click to collapse
That's what I'm currently trying out.
I would never had come up with this assumption, without the wish to understand the logic behind.
Since the nature of this presumable race condition is a fickle ***** (if my assumption is correct),
it may take a while to have solid evidence.
Although, it sounds tempting.
Thank YOU!!!
Thanks for this fix grzwolf, works as it should. Now my P7500 is great with cm10.1 and good battery life. :good:
theone
Question ! Do i have to flash source code or just only p4_kernel_2013.04.10-19.44.zip ? Thanks
saigon66 said:
Question ! Do i have to flash source code or just only p4_kernel_2013.04.10-19.44.zip ? Thanks
Click to expand...
Click to collapse
Just the one you mentioned --> p4_kernel_2013.04.10-19.44.zip
CHN Kernel
grzwolf said:
Just the one you mentioned --> p4_kernel_2013.04.10-19.44.zip
Click to expand...
Click to collapse
Since the Chinese Kernel solo, solves the problem why don't you compare the kernels. Hope i'm not ofending you with probably a stupid question. I'm saying this because when i found Stifmeister zip file and solution, i installed the chinese kernel directly via odin, and just overwrited some network files (i presume), and since then, 8 months ago, never seen a wakelock and a battery drain. Some my humble assumption was that the Chinese Kernel has no l2_hsic wakelock, except, when you connect a USB sd card and unmount it without passing through settings.
Hope it helps.
PS: I should have said this first, i'm still on stock...
Great Job anyway..
Thanks
Phibs said:
Since the Chinese Kernel solo, solves the problem why don't you compare the kernels. Hope i'm not ofending you with probably a stupid question. I'm saying this because when i found Stifmeister zip file and solution, i installed the chinese kernel directly via odin, and just overwrited some network files (i presume), and since then, 8 months ago, never seen a wakelock and a battery drain. Some my humble assumption was that the Chinese Kernel has no l2_hsic wakelock, except, when you connect a USB sd card and unmount it without passing through settings.
Hope it helps.
PS: I should have said this first, i'm still on stock...
Great Job anyway..
Thanks
Click to expand...
Click to collapse
Your suggestion is absolutely conclusive and would be definitely worth a follow up.
Afaik only Samsung knows, what sources and settings were used to build this specific Chinese Kernel,
Means, they are very unlikely available. Otherwise the magic would have been unveiled long time ago.
I suppose disassembling the kernel and looking for the specific code where the wakelock is set would be too difficult?
Sent from my GT-P7100 using Tapatalk 4 Beta
doctorow said:
I suppose disassembling the kernel and looking for the specific code where the wakelock is set would be too difficult?
Sent from my GT-P7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
At least for me.
Afaik it would end up with machine code / assembler language.
Another tool were required to translate it into C.
Even then, there were no really meaningful function and variable names.
Means, one couldn't easily compare this with existing sources.
Finally the whole exercise could result in already known source code.
Not impossible, that the "magic of the China-Kernel" is caused by very specific compiler or optimization settings, which cannot reverse engineered.
Too many if and may be ...
Comparing kernel sources is a very good idea.
Pershoot's p4 kernel is based on Samsungs kernel sources for GT-P7510, Opensource Update 2, released in April 2012 (AFAIR).
For the p5 kernel, I always rebased pershoot's kernel to the latest sources (to GT-P7300_HK_ICS_Opensource_Update1.zip in September, to GT-P7300_ICS_Opensource_Update1.zip in December). No one has ever reported the l2_hsic bug on CM for p5. Neither on CM10 (where I used the chinese kernel sources), nor on CM10.1 (updated to the official ICS sources). But the bug occured for example on AAcount's kernel which isn't rebased. So Samsung seems to fixed the issue in the kernel instead of doing some "magic hacks".
I commited a lot of different p4/p5 kernels to github to make it easier to compare them. I guess you'd like to take a look on those changes:https://github.com/cmorlok/android_kernel_samsung_p5/tree/P7300_ICS_U1/drivers/misc/modem_if
Great, of course I would. Thanks.
Just kdiffed modem_link_device_hsic from your recent P5 against P4, there are non trivial differences.
I'll give it a try right away.
hi c-o-m and grzwolf.
can you please furnish the latest code to this implementation?
any SOD as a result? any other weird behavior?
i'd like to get this in to mainline, if no issue.
thx
pershoot said:
hi c-o-m and grzwolf.
can you please furnish the latest code to this implementation?
any SOD as a result? any other weird behavior?
i'd like to get this in to mainline, if no issue.
thx
Click to expand...
Click to collapse
Following C-o-M's advise with the code review between P4 and P5 modem interface was the breakthru.
The P5 modem interface has a number of non trivial changes compared to its P4 counterpart (--> git format-patch attached).
Although I didn't understand the details, I gave them a try and replaced the P4 modem interface from your github repo completely with the one coming from P5.
Non of the usual test cases made any problem regarding l2_hsic or anything else.
- long time operation
- charging w/o reboot
- USB-drive operation
- Wifi
- 3G
Currently I'm on the 20130604 CM nightly + KernelMod, means 12 days in sequence since last reboot.
BTW: Neither a single SOD, nor any other weird behavior.
To my opinion, the l2_hsic amok issue could be finally closed.
Hail to C-o-M.
Do you think this will get merged into where ever it is that the cm team get their kernals from?
grzwolf said:
Following C-o-M's advise with the code review between P4 and P5 modem interface was the breakthru.
The P5 modem interface has a number of non trivial changes compared to its P4 counterpart (--> git format-patch attached).
Although I didn't understand the details, I gave them a try and replaced the P4 modem interface from your github repo completely with the one coming from P5.
Non of the usual test cases made any problem regarding l2_hsic or anything else.
- long time operation
- charging w/o reboot
- USB-drive operation
- Wifi
- 3G
Currently I'm on the 20130604 CM nightly + KernelMod, means 12 days in sequence since last reboot.
BTW: Neither a single SOD, nor any other weird behavior.
To my opinion, the l2_hsic amok issue could be finally closed.
Hail to C-o-M.
Click to expand...
Click to collapse
cool thx grzwolf.
Lol, shows how much I pay attention. I completely missed pershoots post.
Edit:
Ok, looks like this should be in the nightlies now....
http://forum.xda-developers.com/showpost.php?p=42680093&postcount=1875
Unofficial CyanogenMod 10.1
Rom: Unofficial CyanogenMod 10.1
Android version: 4.2.2
Status: Alpha (means not ready as beta or even stable release!)
What doesn't work:
Sound partially, only calls not working right
Wifi
GPS
Bluetooth
Brightness control
Airplane mode
Camera, did work though in earlier version
Disclaimer
I am not responsible for bricked devices, broken hearts, thermonuclear war or you getting fired because the alarm app failed. It's up to you, not to me.
Click to expand...
Click to collapse
Downloads:
Google Drive CM10.1
Mirror, hosted by Burn02
The version differences:
Code:
24/2/14
[LIST]
[*] Using new audio hall
[*] Microphone works now, call still doesn't
10/2/14
[LIST]
[*] Initial audio support
[*] Fixed Wifi symlink for MAC-adres
[*] ICS_AUDIO_BLOB disabled
[/LIST]
01/12/13
[LIST]
[*] ICS_AUDIO_BLOB enabled
[*] Using original audio blobs
[/LIST]
14/11/13
[LIST]
[*] Both Internal storage and external storage working
[*] Build modified init from source
[*] Dalvik with x86 houdini support
[*] More modules build from source
[/LIST]
6/11/13
[LIST]
[*] Only internal storage working
[*] Libc with x86 wrappers support
[*] Pixelflinger/charger with x86 encoder support
[*] Ramdisk changes
[*] Android Build fixes for x86
[*] Add intel specific codes
[/LIST]
Workarounds:
The Rom can bootloop when installed in TWRP. If so use CWM instead for a while till TWRP is working correctly.
Want to help?
This Rom is made by many people that contribute to it, if it is in code, new information or just bug logs. Everybody can help. Make a 'Logcat' about the problems u encounter and post them here. Give a brief explanation of what u did and wanted to archive (we will try our best to get them sorted, eventually) or contribute with code into my github at the moment.
Click to expand...
Click to collapse
Source:
https://www.github.com/HazouPH
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Hazou said:
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Click to expand...
Click to collapse
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
GalaxyUser said:
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
Click to expand...
Click to collapse
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Hazou said:
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Click to expand...
Click to collapse
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Hazou said:
Unofficial CyanogenMod 10.1
Click to expand...
Click to collapse
Thanks!.. is a great news...
antkalaitzakis96 said:
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Click to expand...
Click to collapse
Y' i know. He asked permission tot post it
Wifi working isn't a very big problem. I want to first hopefully fix the sound, or hope that some ideas might help.
Sent from my GT-P5110 using XDA Premium HD app
Hey can somebody post some screenshots ??
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
great .. thanks @Hazou
Enviado desde mi Moto usando Tapatalk
ICuaI said:
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
Click to expand...
Click to collapse
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
hotpokets said:
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
Click to expand...
Click to collapse
You don't need a screenshot, if this doesn't work yet. This is a thread to make the rom functional. Then it can be released to the regular users like us, who just want to use it regardless of the making process
You can go in every CM10.1-thread in this forum. I am sure that you will find enough screenshots of CM10.1. The rom for our xt890 doesn't have another look.
Or try this alpha-build on your own phone
And now for me I'll stop being of topic
Sorry for that to all the devs
GalaxyUser said:
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
Click to expand...
Click to collapse
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Hazou said:
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Click to expand...
Click to collapse
Will this ROM work on Lenovo K900?
charming.arpit said:
Will this ROM work on Lenovo K900?
Click to expand...
Click to collapse
Not out of the box, no.
Sent from my GT-P5110 using XDA Premium HD app
intel released source code for android 4.4
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Did you guys saw this?
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
drunk_ryder24 said:
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Click to expand...
Click to collapse
hey this is just
Android* 4.4 (KitKat) x86 Emulator System Image
this is for developers who running a pc (x86) and want to emulate the newest android.
this has nothing to do with our fone.
i think the problem is, this image dont got the drivers for our device.or any drivers expect for emulation.. dont know but thanks for the info that intel is developin
regard
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Click to expand...
Click to collapse
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Addendum: Unified builds, in particular this one for moto_msm8960 devices:
Supposed list of unified devices: Previous RAZR HD, Photon Q, Atrix HD, etc. : xt897, xt901, xt905, xt907, xt905, xt925, xt926, mb886 are now:
Now: moto_msm8960
I'm going to put them in a list so I can get around to checking Y on known working ones, and N on known non-working ones:
- xt926 (Y)
- xt925 (Y)
- mb886 (Y)
- xt897 (Y)
- xt901 (?)
- xt905 (?)
- xt907 (Y)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Quick notes about unified devices:
Do they all work in this build? I have no idea, but am pretty sure that from feedback that xt926/5, xt907 and xt897 have been reported to work.
The bottom line is that I rely on anyone reading here (or who is directed here from their development pages) to let me know what works, what doesn't so please let me know.
----------------------------
Download links
Latest versions built by me can be found here: (currently 6.xx.* and up).
Note: 6.58.7 final/stable is the latest (see the main development thread if not understood)
Changelogs:
v6.58.7 - new code and fixes
Click to expand...
Click to collapse
6.43.6 (02.06.2014)
- fix recursive path creation bug for /data/media/0
- default to /data/media/0 unless we define BOARD_HAS_NO_MULTIUSER_SUPPORT
- use lstat to check if file exists
6.43.4 - Final, Stable
- fix text print color could persist after md5 check
6.42.9 - Final & Stable
- default again to libtar for backup/restore
6.42.7 - Stable
- default to busybox tar:
- use busybox tar by default as it now supports selinux context backup/restore
- unify libtar and busybox tar options (-p for selinux context)
- remove now deprecated external selinux container code
6.41.6 - Stable & perhaps Final
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
6.41.5 - Stable
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
Click to expand...
Click to collapse
- Unified msm8960: 6.58.7 (4.4.4): Image : http://d-h.st/2xD
- v6.43.6: Unified msm8960: http://d-h.st/HgH
- v6.43.4: Unified msm8960: http://d-h.st/sQQ
- v6.42.9: Unified msm8960: http://d-h.st/SjY
- v6.42.7: Unified msm8960: http://d-h.st/9pD
- v6.41.6: Unified msm8960: http://d-h.st/uq1
- v6.41.5: Unified msm8960: http://d-h.st/QiK
Click to expand...
Click to collapse
Note: tested only on my xt926. Aroma has a few little glitches but is not often maintained.
Older versions built by Phil (or his 'crew'):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt926 // oldest (and substitute your dev name for pre-unified builds)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960 // newer, recent.
Click to expand...
Click to collapse
My github(just created/work-in-progress) for tracking changes on this: https://github.com/Hachamacha/philz.git
Click to expand...
Click to collapse
Note: My part in this is very minuscule. I just got (git) his source and stuck it into cm11 as a build base. I changed very little, only added the msm8960 build since I think phil is working on the source rather than many individual builds due to time. If you look at his github from the main page link, the only file I really changed was ./boardconfig/BoardConfig.mk under ./recovery.
Goal: Just to make this available and keep people out of the main thread that aren't developing. If I can help with the specific device I'd do it, but I'm really not an xt926/5 expert. Still, if you've got msm8960 questions (so: device-specific, not general philz touch) ask them here about the device and recovery since odds are better you'll get an answer here than in the main thread. I'll try to update this with latest builds each week.
Disclaimer: The usual stuff you read in all of these threads. If your mind turns into margarine after installation, please send a sample to the CDC labs in Virginia. I searched all over XDA for a thread for philz for the msm8960 but didn't find it. If you do, feel free to destroy this thread, call me names, threaten my relatives (please do this), etc.
Credits: I think all credit should go to Phil, @Orphee and the CM11 guys if you like this type of recovery.
Thanks for doing this bro. Otherwise AHD'd be on 6.0.7x..
EDIT: Great job, I can confirm, 6.22.1 flashes and screen touches work perfect, format, wipe clean new rom, install new rom, restore backup on the Atrix HD/mb886.
Who wouldn't like the best recovery of all? Right? Thanks a lot
Works with keys only on the 907. Thanks.
aviwdoowks said:
Works with keys only on the 907. Thanks.
Click to expand...
Click to collapse
I don't recall the xt907 being unified into the msm8960, at least not in the philz code, but I could be wrong. Could you try a recent (6.19.x) build from over here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt907 and let me know if that works? I think the msm8960 so-called unified builds are still a bit confused. It looks to me like only xt926 and 5 are covered.
If the build I linked to works, then it's to do with the 'unified' setup and I might need to grab some vender ID's etc.
By saying "works with keys only": I assume you're saying that the touchscreen stuff is off-kilter or just off period?
Thanks and I'll look it over for that device.
Everyone else: Glad it's working out for you. I'll update as soon as there's another git update.
No touch function at all. The mb886, 'hd & photon Q (screen input works too, albeit mirrored) recoveries have always worked on the M.
Any can be used on the others for key only use.
The Q twrp works 100% on the m but mirrored input. Arrrghhh said he may port his version to the m.
Since we can have unified recoveries now, would it be possible to make TWRP and have it work for all the unified devices?
Sent from my ATRIX HD using Tapatalk
aviwdoowks said:
No touch function at all. The mb886, 'hd & photon Q (screen input works too, albeit mirrored) recoveries have always worked on the M.
Any can be used on the others for key only use.
The Q twrp works 100% on the m but mirrored input. Arrrghhh said he may port his version to the m.
Click to expand...
Click to collapse
Took a look at the cm11 base I'm using as a building platform for philz code and it appears xt907 isn't yet part of the unified group though it ought to be according to CM. I'll leave a note and see if that's in the works. I'll check if xt907 has it's own build over there. By the way, from your reply I wasn't sure if you'd tried the pre-unified version I linked to on goo.im? Also philz stuff is using his own touch library GUI these days, and there might be something about that and the 907. Got some stuff to figure out.
Looks like (Atrix HD, Electrify M, Photon Q, Razr HD, and Razr M) are supposed to be part of it but from the way the code looks, (boardconfig) , not sure I believe it's yet been worked out. Razr M has some 9xx x {?} resolution, right?
Edit: CM11 looks fine as far as unified for xt907, so it must be something in the philz code that's not yet ready for the full array of unified devices.
penser said:
Since we can have unified recoveries now, would it be possible to make TWRP and have it work for all the unified devices?
Sent from my ATRIX HD using Tapatalk
Click to expand...
Click to collapse
I've used TWRP and like it a lot, but haven't looked at the build requirements yet. It seems possible to do unified builds for anything especially if you can do something like build the cm11 default code with it's default recovery, then substitute TWRP recovery for the default CWM in the ./bootable/recovery code. TWRP would have to be setup for that which is something I don't know. CM11 is where the unified structure is coming from in the case of these recoveries.
The 6221 you posted works.
aviwdoowks said:
The 6221 you posted works.
Click to expand...
Click to collapse
Cool! Thanks for letting me know.
hachamacha said:
Cool! Thanks for letting me know.
Click to expand...
Click to collapse
Are you savvy enough to allow/provide a partition backup of /persist?
At least Philz no longer lets noobs format it. Why not back it up? As it gets clobbered often.
---------- Post added at 09:41 AM ---------- Previous post was at 09:22 AM ----------
Could it have been the previous presence/oversight of the fomat command the the cwmr base gave be used on the phones that is the sole cause of all the /persist hubub & it being only on the phone is not an issue?
---------- Post added at 10:17 AM ---------- Previous post was at 09:41 AM ----------
More on persist
http://forum.xda-developers.com/showthread.php?t=2589790
aviwdoowks said:
Are you savy enough to allow/provide a partition backup of /persist?
At least Philz no longer lets noobs format it. Why not back it up? As it gets clobbered often.
---------- Post added at 09:41 AM ---------- Previous post was at 09:22 AM ----------
Could it have been the previous presence/oversight of the fomat command the the cwmr base gave be used on the phones that is the sole cause of all the /persist hubub & it being only on the phone is not an issue?
Click to expand...
Click to collapse
savvy: I don't know the answer to that yet
I just took a look at a) the main thread, noticed this (http://forum.xda-developers.com/showthread.php?p=48940651&highlight=persist#post48940651) and b) the code. What I come up with is that while in recovery, I can go to 'mounts' and mounting "persist" is an option which works for me. It's not on the backup list, mounted or not, but shows up in aroma FM when it's mounted. That link I put there claims there is allowed 5 "extra" partitions for backup/restore, so I might be able to set up /persist as one of them. I'm still new to this recovery code for android so don't expect too much. Looks like if I can get it to work on mine, then it ought to on yours.
As a workaround (if ADB is working to your box in recovery) , you could yank (pull) that /persist stuff yourself, but I think a new version is coming along pretty soon and I'll try to see if I can get it to work. (Time permitting etc etc)
edit: I realized that /persist is in the recovery.fstab file when I build which is why it's a mount choice in that menu. The other stuff (make it a backup choice) appears to be hard-coded in one of the .c files so it could be added, but there's a fair amount of stuff to do to add it. Yeah, it could be modified, but I'd want to ask Phil about it before messing with it. I suspect he had some reason since I noticed you and he talked about this in the main thread. Did he ever get back to you?
Mount is ok. When I posted the now unavailable format was there.
aviwdoowks said:
Mount is ok. When I posted the now unavailable format was there.
Click to expand...
Click to collapse
I'm trying to reopen the discussion in the main thread so we'll see how that goes.
Edit: General build update.
There's a new build, same version but some fixes that I'll put up eventually here. CM11 probably has the newest API and I'm restructuring my environment, so need to sync and clobber repo, include philz as a localrepo. Might take .. all day for the syncing and building to complete. Doing this in a VM today
Fixed: Aroma now works with screen input when booted from the msm version while key only from philz.
Translation: aroma works fully while using this on a 907.
hachamacha said:
savvy: I don't know the answer to that yet
I just took a look at a) the main thread, noticed this (http://forum.xda-developers.com/showthread.php?p=48940651&highlight=persist#post48940651) and b) the code. What I come up with is that while in recovery, I can go to 'mounts' and mounting "persist" is an option which works for me. It's not on the backup list, mounted or not, but shows up in aroma FM when it's mounted. That link I put there claims there is allowed 5 "extra" partitions for backup/restore, so I might be able to set up /persist as one of them. I'm still new to this recovery code for android so don't expect too much. Looks like if I can get it to work on mine, then it ought to on yours.
As a workaround (if ADB is working to your box in recovery) , you could yank (pull) that /persist stuff yourself, but I think a new version is coming along pretty soon and I'll try to see if I can get it to work. (Time permitting etc etc)
edit: I realized that /persist is in the recovery.fstab file when I build which is why it's a mount choice in that menu. The other stuff (make it a backup choice) appears to be hard-coded in one of the .c files so it could be added, but there's a fair amount of stuff to do to add it. Yeah, it could be modified, but I'd want to ask Phil about it before messing with it. I suspect he had some reason since I noticed you and he talked about this in the main thread. Did he ever get back to you?
Click to expand...
Click to collapse
Currently, recovery doesn't allow backup/restore of all what's in fstab
It would be dangerous in my opinion as you sometimes have the bootloader there
try to edit this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /preload ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
setting the mountpoint to preload will add it to my mod as it supports that partition
However, restoring could fail if you do not add the selinux needed permissions
Also, you can follow my guide here to add extra partitions using this flag: EXTRA_PARTITIONS_PATH
Actually, without adding the flag or recompiling, you can just edit recovery.fstab to:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /extra_part1 ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
by default, it is enabled when you name it extra_part1 to extra_part5
That way, you can easily add support to 5 extra partitions to nandroid menu with just a repack, no recompile needed
Phil3759 said:
Currently, recovery doesn't allow backup/restore of all what's in fstab
It would be dangerous in my opinion as you sometimes have the bootloader there
try to edit this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /preload ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
setting the mountpoint to preload will add it to my mod as it supports that partition
However, restoring could fail if you do not add the selinux needed permissions
Also, you can follow my guide here to add extra partitions using this flag: EXTRA_PARTITIONS_PATH
Actually, without adding the flag or recompiling, you can just edit recovery.fstab to:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /extra_part1 ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
by default, it is enabled when you name it extra_part1 to extra_part5
That way, you can easily add support to 5 extra partitions to nandroid menu with just a repack, no recompile needed
Click to expand...
Click to collapse
Thanks for the tips. After I test the next version (6.23.x) I'll try these techniques out, see how it goes on mine.
hachamacha said:
Thanks for the tips. After I test the next version (6.23.x) I'll try these techniques out, see how it goes on mine.
Click to expand...
Click to collapse
also, take a look here, at the highlighted line:
https://github.com/CyanogenMod/andr...8960/blob/cm-11.0/device_moto_msm8960.mk#L121
You have also a ro property to forbid mount:
Code:
ro.cwm.forbid_mount
Both these properties affect the format/mount options in "Mounts and Storage" menu
As far as screen input for the 907 goes, are you not almost there if aroma works?
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
It works on 6227.