Hey guys, so we have a pretty great CM9 rom by Sportstar, so I'm going to post some logcats I've gotten from a working sense 3.6 rom of the radio, and then one from the CM9 build!
When getting a log cat, use this command in adb:
Code:
abd logcat -b radio
Here is the logcat with a working radio (taken from a sense 3.6 ROM):
http://logcat.miui.us/912009
Here is the logcat with a broken radio (the June 13th build of CM9 from sportstar):
http://logcat.miui.us/905004
Here is the logcat running the commands:
Code:
netcfg rmnet0 up
netcfg rmnet0 dhcp
(the June 13th build of CM9 from sportstar):
http://logcat.miui.us/906007
Here is a logcat trying to get local APNs (the June 14th build of CM10 from sportstar):
As well as getting these errors upon bootup:
E/MobileDataStateTracker( 331): default: Ignoring feature request because could not acquire PhoneService
E/MobileDataStateTracker( 331): default: Could not enable APN type "default"
Click to expand...
Click to collapse
http://logcat.miui.us/914004
Here is the logcat with an old SIM card (the June 14th build of CM10 from sportstar):
http://logcat.miui.us/917008
It seems to be a problem reading the SIM / Baseband / libsqlite, possible fix's here:
#1.
in build.prop, find the line: ro.modversion=9.0.0-RC0-p990-UNOFFICIAL (near the buttom) and just delete it, and your baseband is working.
Click to expand...
Click to collapse
Source:
http://forum.xda-developers.com/showthread.php?t=1631607
#2.
These two sites explain all that's going on in the logcat (or makes it more readable)
Click to expand...
Click to collapse
Source:
http://www.netmite.com/android/mydroid/hardware/ril/include/telephony/ril.h
http://hi-android.info/doc/com/android/internal/telephony/RILConstants.html#CDMA_CELL_BROADCAST_SMS_DISABLED
#3.
They refer to the appdb version being the issue, and there does seem to be a pretty big discrepancy there. Could we just update the appdb version to match?
Click to expand...
Click to collapse
Source:
https://github.com/ahmetalpbalkan/orman/issues/42
Here's to getting a fully working AOSP ROM!
dubt17 said:
Hey guys, so we have a pretty great CM9 rom by Sportstar, so I'm going to post some logcats I've gotten from a working sense 3.6 rom of the radio, and then one from the CM9 build!
Here is the logcat with a working radio (taken from a sense 3.6 ROM):
http://tinypaste.com/ff5db381
Here is the logcat with a broken radio (the June 13th build of CM9 from sportstar):
http://tinypaste.com/49da362a
Here's to getting a fully working AOSP ROM!
Click to expand...
Click to collapse
When posting logcats use logcat.miui.us
sportsstar89 said:
When posting logcats use logcat.miui.us
Click to expand...
Click to collapse
Logcats uploaded to new site!
So I installed the new CM 10 and ran a logcat while trying to get local APNs. The relevant portion is here.
Also got these 2 lines on boot:
E/MobileDataStateTracker( 331): default: Ignoring feature request because could not acquire PhoneService
E/MobileDataStateTracker( 331): default: Could not enable APN type "default"
So its a problem with libsqlite
Sent from my HTC_Amaze_4G using xda premium
sportsstar89 said:
So its a problem with libsqlite
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Could it simply be a permissions issue?
phoenix79 said:
Could it simply be a permissions issue?
Click to expand...
Click to collapse
Nope
sportsstar89 said:
Nope
Click to expand...
Click to collapse
Lol, I'm a windows admin. Linux permissions suck
So what I was thinking maybe correct with it not being able to read the new SIM? I have contacted a few developers from M3 that helped out with this issues and hopefully they can point us in a good direction.
Took some time to search around and found this: (similar error, unrelated problem)
https://github.com/ahmetalpbalkan/orman/issues/42
They refer to the appdb version being the issue, and there does seem to be a pretty big discrepancy there. Could we just update the appdb version to match?
I posted this on Sportsstars CM10 thread.
For those with Old SIM Cards (3-4yrs old) please try this command in ADB or Terminal
Code:
netcfg rmnet0 up
netcfg rmnet0 dhcp
It's supposed to force data on. Someone please test and report.
Got it, didn't find my old sim, but just ran the commands on my new one, posting logcat on the first post!
New links that were provied are up! Along with some more logcats!
Double0EK said:
I posted this on Sportsstars CM10 thread.
For those with Old SIM Cards (3-4yrs old) please try this command in ADB or Terminal
Code:
netcfg rmnet0 up
netcfg rmnet0 dhcp
It's supposed to force data on. Someone please test and report.
Click to expand...
Click to collapse
I'll try it once I make a nandroid
Sent from my Energized HTC Amaze!
Double0EK said:
I posted this on Sportsstars CM10 thread.
For those with Old SIM Cards (3-4yrs old) please try this command in ADB or Terminal
Code:
netcfg rmnet0 up
netcfg rmnet0 dhcp
It's supposed to force data on. Someone please test and report.
Click to expand...
Click to collapse
I've had the same Tmo SIM (current sif I use now) from 2006-07 I'll test whatever needs to be done as long as someone directs me as to what to do. Also I have about 2 or 3 of those old sim cards that I can send to you if you need one. You just need to activate em I believe .
The SIM should be active for the commands to work. I hope someone can come through and pull a logcat on an AOSP/CM Rom if they got data to turn on. Then the devs can build from there.
Oh, I forgot about the new simcard thing, that really could be a factor..
And can I say it is about time that the users help devs debug? It makes me happy to see someone help direct users how to help figure things out..
Sent from my NookColor using xda app-developers app
I have a new sim or I'd help... (I got my sim card like 4months ago)
Any chance running the commands on the new sim would help?
Sent from my epic amaze 4g
Well I think I'm on the right road I was able to get the ril to find rild
Sent from my HTC_Amaze_4G using xda premium
I did the commands but data didn't turn on for me. It Said permission denied.
Sent from my Energized HTC Amaze!
Related
We have found a solution for:
MDJ's Gingerbread RAM 1.0 RC5
And
Darkstone superRAM v1.5 build
MAsterokki posted the solution.
replace the original system.ext2 with this on.
His post Was Updated
For the DEVs there is a folder filled with working PPP folders for various builds based on devices.
Both the system.ext2 and the folder with PPP options for DEVs can be found here.
(as soon as they are uploaded)
In the folder you can now find the system.ext for Dandiest's Desire Z v0.3.1n, for Darkstone's superram Froyo v1.5 and Superram Sense v0.1 and for MDJ Gingerbread RC5
-----------------------------------
Let's all say Thanks to MAsterokki
and use his thanks button!
-----------------------------------
If you dont have data issues, dont use this system.ext2
-----------------------------------
DutchDanny said:
We have found a solution for:
MDJ's Gingerbread RAM 1.0 RC5
And
Darkstone superRAM v1.5 build
MAsterokki posted the solution.
replace the original system.ext2 with this on.
His post
-----------------------------------
Let's all say Thanks to MAsterokki
and use his thanks button!
Click to expand...
Click to collapse
whats does this do to the Super Ram build
guntcent said:
whats does this do to the Super Ram build
Click to expand...
Click to collapse
If you cant' get data to work this will fix it, would be my guess from the bold subject of No Data, but it could be more clear I guess....
crisisinthecity said:
If you cant' get data to work this will fix it, would be my guess from the bold subject of No Data, but it could be more clear I guess....
Click to expand...
Click to collapse
Greaat Guess ! ! !
Any technical explanation for what this fix is? Something about PPP settings doesn't really explain much. Data works fine for me on RC5 Gingerbread but I'm not on Vodafone. Without any details I don't know how this will/can impact me.
OCedHrt said:
Any technical explanation for what this fix is? Something about PPP settings doesn't really explain much. Data works fine for me on RC5 Gingerbread but I'm not on Vodafone. Without any details I don't know how this will/can impact me.
Click to expand...
Click to collapse
Well this actually should be a disclaimer in the topic start. If you dont have data issues, dont use my system.ext2.
The PPP setttings were replaced with the ones from an earlier build.
BTW, I got The desire Z build, v0.3.1n working with Vodafone NL and it might also solve some problems other people may have with the Deire Z build made by Dandiest. It will be up in a few minutes.
MAsterokki said:
Well this actually should be a disclaimer in the topic start. If you dont have data issues, dont use my system.ext2.
The PPP setttings were replaced with the ones from an earlier build.
BTW, I got The desire Z build, v0.3.1n working with Vodafone NL and it might also solve some problems other people may have with the Deire Z build made by Dandiest. It will be up in a few minutes.
Click to expand...
Click to collapse
There's always the data freeze with PPP but that seems to be an altogether different issue.
Superram Sense build
The working system.ext2 for the superram Sense v0.1 build will be up in a few minutes.
I have also uploaded a folder with build specific working PPP folder for DEVs in the same link. These PPP settings are not just working for the Vodafone NL phones, but have been reported to work on many worldwide providers.
The PPP freeze OCedHrt is talking about may be solved with the new Darkstone Sense build (I spotted he used some different settings that might benefit the PPP upkeep)
MAsterokki said:
The working system.ext2 for the superram Sense v0.1 build will be up in a few minutes.
I have also uploaded a folder with build specific working PPP folder for DEVs in the same link. These PPP settings are not just working for the Vodafone NL phones, but have been reported to work on many worldwide providers.
The PPP freeze OCedHrt is talking about may be solved with the new Darkstone Sense build (I spotted he used some different settings that might benefit the PPP upkeep)
Click to expand...
Click to collapse
You're great!
I didn't read up yet, is Vodafone working in the new Desire_Z 0.3.2??? (downloading right now...)
pietrucci said:
You're great!
I didn't read up yet, is Vodafone working in the new Desire_Z 0.3.2??? (downloading right now...)
Click to expand...
Click to collapse
Version 0.3.2 is just a small bugfix, not a build So yes it will still work
MDJ Ginger RC5
still data don't work after phone call
Spirit81 said:
MDJ Ginger RC5
still data don't work after phone call
Click to expand...
Click to collapse
That is annoying Is your provider 3G?
Did you mess about in the *#*#4636#*#* menu before or after replacing the original system.ext with mine?
MAsterokki said:
Version 0.3.2 is just a small bugfix, not a build So yes it will still work
Click to expand...
Click to collapse
Right, didn't look too good (it was late this night)...
MAsterokki said:
That is annoying Is your provider 3G?
Did you mess about in the *#*#4636#*#* menu before or after replacing the original system.ext with mine?
Click to expand...
Click to collapse
yes, my provider is 3g, but at the moment i am using 2g...
just tried on 3g, do phone call, and data is working after that..
Same here. After a call it stops working. If i manually turn it off and on, starts working again.
NEVER had data connection with superRAM FroYo since released. Now I finally have .
Data connection stable for 3 days in a row, no drops @ all.
superFIX FroYo... thumbs up.
This is great! thank you very much!
Data works!
Does this work with MIUI RAM build?
Sent from my htc_bravo using XDA App
Beretta93 said:
Does this work with MIUI RAM build?
Sent from my htc_bravo using XDA App
Click to expand...
Click to collapse
I am still busy with that issue, but I cant seem to find anything wrong with it... It might take some more time.
Hi there,
As I am developing my first apps for Android, I've run into an issue that bothers me. When trying to logcat (via terminal or Eclipse), this is the output I get:
Unable to open log device '/dev/log/main': No such file or directory
Click to expand...
Click to collapse
I've googled, but found solution only for Huawei devices (getting into service menu and activating logging) but it doesn't work with my P500. Everything (deploying , debugging) works just fine. BTW I am using NightlyFourE V4.1 ROM (that's Cyanogenmod 2.3.7) and linux workstation. Any help appreciated!
Sent from my LG-P500 using Tapatalk
Look for a tweak the same as that on the /system/etc/init.d folder
rm -r dev/log/main
or something similar to that and delete it..
Sent from my LG-P500 using Tapatalk
Coffei said:
Hi there,
As I am developing my first apps for Android, I've run into an issue that bothers me. When trying to logcat (via terminal or Eclipse), this is the output I get:
I've googled, but found solution only for Huawei devices (getting into service menu and activating logging) but it doesn't work with my P500. Everything (deploying , debugging) works just fine. BTW I am using NightlyFourE V4.1 ROM (that's Cyanogenmod 2.3.7) and linux workstation. Any help appreciated!
Click to expand...
Click to collapse
next you should use stock roms for testing and developing applications not modded ones
dnle71 said:
Look for a tweak the same as that on the /system/etc/init.d folder
rm -r dev/log/main
or something similar to that and delete it..
Click to expand...
Click to collapse
Thanks a bunch man! Worked like a charm..
trettet said:
next you should use stock roms for testing and developing applications not modded ones
Click to expand...
Click to collapse
I guess I should, but as long as it's my daily-driver I think I will prefer custom ROMs (i'm definitely not full-time developer, just a fan)..
Ok, guys here's the link of the ParanoidAndroid ROM i have been trying to port from One V. I have the permission from 1ceb0x.
LINK: http://d-h.st/Rkj
Gapps: http://d-h.st/ul6
Thanks to 1ceb0x, for giving me permission to use his ROM, and Lloir for his CM9 base...
How to flash:
1. take a nandroid backup.
2. wipe cache and data
3. go to fastboot mode and connect your phone to pc
4. place system.img in the same directory as fastboot
5.open command line (terminal) and go to your fastboot directory
6. type fastboot flash system system.img
7. reboot
We really need stable 4.1 AOSP for me to continue working on this. Waiting.
Changelog
Code:
0.1-----Initial build
0.2-----Used Lloir's vendor and device trees, tweaked build.prop, removed hTC crap
0.3-----Rebased, now using Lloir's CM9. Also, link is now on Dev-Host.
0.4-----Fixed updater-script.
0.5-----Now ROM packed in system.img
Stereo8 said:
Ok, guys here's the link of the ParanoidAndroid ROM i have been trying to port from One V. I have the permission from 1ceb0x.
LINK: https://dl.dropbox.com/u/65113140/Desire_X_ParanoidAndroid_2.50_JB_4.1.2.zip
Gapps: https://dl.dropbox.com/u/65113140/gapps-jb-20121017-KonstaKANG.zip
Thanks to 1ceb0x, for giving me permission to use his ROM, and infernal77, for making a 1.18 software base...
Test this for me guys and I'm not responsible if anything happens to your device.
Good luck!
Click to expand...
Click to collapse
Cool! , just one problem dude you used the HTC Desire X Sense 1.18 as a base which is impossible since you need AOSP, AOKP, CM10 or any other Jellybean ROM for the Desire X as a base for this to boot , or am I wrong? but anyway testing
The Android Manual said:
Cool! , just one problem dude you used the HTC Desire X Sense 1.18 as a base which is impossible since you need AOSP, AOKP, CM10 or any other Jellybean ROM for the Desire X as a base for this to boot , or am I wrong? but anyway testing
Click to expand...
Click to collapse
yea, I thought something like that will happen... Well if it boots then I'm awesome, right..
Stereo8 said:
yea, I thought something like that will happen... Well if it boots then I'm awesome, right..
Click to expand...
Click to collapse
Yeah
ROM updated. I used system/lib, etc, and bin files from Lloir's device tree.
Does it boot?
Sent from my HTC Desire X using xda premium
I have no ideaaa... I don't have the phone...
Sent from my ToasterOven running Toastdroid 4.2
Hey stereo, I tried it, didn't boot (stopped at the HTC logo), here's the logcat
https://www.dropbox.com/s/lb05u0rmbleqlym/logcat_booting.txt
infernal77 said:
Hey stereo, I tried it, didn't boot (stopped at the HTC logo), here's the logcat
https://www.dropbox.com/s/lb05u0rmbleqlym/logcat_booting.txt
Click to expand...
Click to collapse
that's not even a whole lolcat
Lloir said:
that's not even a whole lolcat
Click to expand...
Click to collapse
Ok, don't know what I did wrong, it's "adb logcat >logcat.txt" when you reboot out of recovery after flashing, right ?
edit: Ok, here's what I did second time : full wipe, flash the rom and google apps, then opened my platform-tools folder and typed "adb logcat -v long >logcat.txt" which gave me this : https://www.dropbox.com/s/gszb1ked7e8yjky/logcat.txt
Like first try, the phone hangs during boot, with HTC logo
Stereo8 said:
I have no ideaaa... I don't have the phone...
Sent from my ToasterOven running Toastdroid 4.2
Click to expand...
Click to collapse
Which phone have you previously used? If you wanna blind port, you should at least have some experience of an HTC device before. Just saying ....
Regards
Sent from my HTC Desire X using xda app-developers app
Finally I uploaded the newest build to Dropbox... It includes:
- Lloir's system/lib, etc, and bin files...
-Superuser instead of SuperSU
-Removed hTC crap
-Removed hTC crap from build.prop
-Tweaked build.prop
infernal77 said:
Hey stereo, I tried it, didn't boot (stopped at the HTC logo), here's the logcat
https://www.dropbox.com/s/lb05u0rmbleqlym/logcat_booting.txt
Click to expand...
Click to collapse
dude try porting CM9 fist because there is a base available for it all you need is permission from Llior and a boot.img for CM9
The Android Manual said:
dude try porting CM9 fist because there is a base available for it all you need is permission from Llior and a boot.img for CM9
Click to expand...
Click to collapse
Um, I'm not sure if I'll be able to, I've been trying to get an angle on how all this stuff works and I get the basics but when I look at github, it's like Chinese to me (or Taiwanese, since its HTC). I've looked at countless guides to port CM9, set up VMWare and Ubuntu 10 but it's a steep learning curve. Last month I maxed out our bandwidth (100 gig) trying to set up a local mirror for the source, which kind of defeated the purpose :laugh:
infernal77 said:
Um, I'm not sure if I'll be able to, I've been trying to get an angle on how all this stuff works and I get the basics but when I look at github, it's like Chinese to me (or Taiwanese, since its HTC). I've looked at countless guides to port CM9, set up VMWare and Ubuntu 10 but it's a steep learning curve. Last month I maxed out our bandwidth (100 gig) trying to set up a local mirror for the source, which kind of defeated the purpose :laugh:
Click to expand...
Click to collapse
Source of cm9 is 7gb including all proto device trees .you need an extra 15 gb just for building. I'll help you set all things up, you just have to put in some effort and time....My build from source is ready. Uploading.
Regards
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Source of cm9 is 7gb including all proto device trees .you need an extra 15 gb just for building. I'll help you set all things up, you just have to put in some effort and time....My build from source is ready. Uploading.
Regards
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Here you go
http://d-h.st/QmB
regards
Sent from my HTC Desire X using xda app-developers app
Any test results?
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Any test results?
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Status 7 (No error Message)
The Android Manual said:
Status 7 (No error Message)
Click to expand...
Click to collapse
OK, back to topic, I'll test stereo's new one, this is his thread
Yasir, why not make a joint thread by anyone here that wants to participate in getting a CM9 to the DX ?
"Project DX" or something, hopefully there's as many people showing up to the party as in Project X (the movie) lol
when you do logcats let it run for about 5minutes -.- also for status 7 just do a recovery log (go to report error under advanced) and put it here i'll check back later
Hey all, since a lot of folks are wondering about custom roms for the DX, I decided to start this thread to document my exploits in trying to compile CM9.
Basically, I'm new to Android (had an iPhone 3GS for about 2 years) so I'm going to need a lot of help and this is really going to start of very basic. But since I had my Desire X and been on this forum, I have met more and more cool people that are actively trying to help development for our phone, like stereo8,maartenxda and yasir, so I'm sure we'll be alright. None of this would be even possible if not for LLior that made the CWM recovery for us. :good:
OK, so to build CM9 you need a build environment set up specifically for the job, there's many guides out there on how to do this, but I found this one (props to mbroeders, OP of the tut) pretty good :
http://forum.xda-developers.com/showthread.php?t=1566224
Basically, building CM9 is done in linux, Ubuntu being the most popular version, and I'll be using the latest Ubuntu 12. If you don't use Ubuntu as main OS, you can still try this, but you'll need to set up a good (!) portion of your harddrive to install it in a virtual environment, like VMWare Player (free). Mind you, we'll be downloading the CM9 source, which ended up being around 10 gig on my pc, and we'll be needing at least another 16 gig to actually build CM9. To be on the safe, I set aside 50 gig on my drive for the virtual Ubuntu-pc in VMWare.
The guide I'm using will show you how to set up a general build environment, but since we are talking about the Desire X, which is brand new and without official CM support (yet?), we are going to have to adapt it to make CM9 for our phone. Several people have already worked on this, mainly Lloir, so I got his permission to use the stuff he's already done. A big thanks btw, from one and all
And this is basically the first time I'm going to need help. To adapt the build system specifically for the DX, we'll need to make a local_manifest file that points it to device and vendor trees LLoir has made. The local_manifest is supposed to go in the .repo folder of your CM9 source.
How do I do this ?
Goto cm9 wiki and install all prerequisites. Then do a repo init of the main build tree(cm9) and then add the device trees to manifest.xml found in .repo. after that , you sync via repo sync and then you setup environment through envsetup.sh and then you build for protou by brunch protou. Debug the errors you encounter. That's about it. If it doesn't boot after successful build, then the device/hardware/vendor/kernel trees need some sorting out .
Regards.
Sent from my HTC Desire X using xda app-developers app
help for local_manifest - Llior ?
Morning, googled some more, and found a template for a local_manifest.xml file I'm adapting for the DX.`I prefer to go as much by the book as possible for now, apparently putting these in manifest.xml can mess up your source.
So far, I have :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Lloir/protou" path="device/htc/protou" remote="github" revision="ics"/>
<project name="LLior/XXXXXXXXXXXXX" path="device/htc/msmXXXX-common" remote="github" revision="ics"/>
<project name="Lloir/android_vendor_htc_protou" path="vendor/htc/protou" remote="github" revision="ics"/>
<project name="Llior/XXXXXXXXXXXXX" path="kernel/htc/msmXXXX" remote="github" revision="XXXXXXXXXXXX"/>
</manifest>
The XXXX need editing, not sure which repositories though
manifest
Here you go, you can see it for your reference...
Attachment
CM9 - first build - result
Yasir Javed Ansari said:
Here you go, you can see it for your reference...
Attachment
Click to expand...
Click to collapse
OK, using your manifest, I managed to set up the system to build with Lloir's device and vendor trees.
I had to edit the msm7x30.mk file in /device/htc/msm7x30-common though so the first section of it would point to /frameworks/base rather than /frameworks/native as in the original for it to build.
It then compiled to the end, I ended up with a boot.img, recovery.img, system.img and userdata.img, which I turned into a .zip file to flash in CWM.
It installs, but gets stuck on the HTC-logo screen, but I can't take a logcat -same as with stereo's paranoidandroid : logcat.txt says logcat cant be found in /sbin/sh- even when I create a sbin/sh folder with logcat.
Anyone know what I'm doing wrong ? I would really like to see what's going on during boot.
infernal77 said:
OK, using your manifest, I managed to set up the system to build with Lloir's device and vendor trees.
I had to edit the msm7x30.mk file in /device/htc/msm7x30-common though so the first section of it would point to /frameworks/base rather than /frameworks/native as in the original for it to build.
It then compiled to the end, I ended up with a boot.img, recovery.img, system.img and userdata.img, which I turned into a .zip file to flash in CWM.
It installs, but gets stuck on the HTC-logo screen, but I can't take a logcat -same as with stereo's paranoidandroid : logcat.txt says logcat cant be found in /sbin/sh- even when I create a sbin/sh folder with logcat.
Anyone know what I'm doing wrong ? I would really like to see what's going on during boot.
Click to expand...
Click to collapse
Stock Rom showed our device shares common config from msm7k and not msm7x30. I'll try another build with some modified things to see if it boots . One thing you can do is to compare lloir device tree with other trees of similar devices to verify whether we are missing something critical. Also did you use pre.built kernel ?
AND framework native is used in jelly bean , not ics. You're syncing jelly bean cm source and device tree is currently for ics. Recheck please.
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Stock Rom showed our device shares common config from msm7k and not msm7x30. I'll try another build with some modified things to see if it boots . One thing you can do is to compare lloir device tree with other trees of similar devices to verify whether we are missing something critical. Also did you use pre.built kernel ?
AND framework native is used in jelly bean , not ics. You're syncing jelly bean cm source and device tree is currently for ics. Recheck please.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Hm, thanks for the input, Yasir. I was wondering about it, I just synced using the default.xml in the last post. I guess that means I was using the prebuilt kernel as well. Don't worry about the source code I synced, it's definitely cm-ics. As far as I can see, there aren't files relating to msm7k in Lloir's github. I'll see if I can find out about a device that uses the msm7k.
cheers :good:
EDIT : Yasir and me are working together on trying to get a CM9 to the Desire X, anyone that wants to help (preferably with experience) is welcome Use this thread to keep things organised. Thanks
update on CM9 - wip - all help welcome !
OK, update on what's happening :
Because our phone has a new Qualcomm processor there's no CyanogenMods out yet for any device that uses it, let alone by HTC, that we can compare it to. This could help us out a lot to get the device specific information and sources the build system needs to make us a CM9. This info and these files are contained in and referred to by the so-called device and vendor trees. Lloir has done the most work for the Desire X up to now in making these device and vendor trees, but since first test builds aren't booting, Yasir and me are going over them again.
By the way, if anyone knows more about why logcat doesn't work, that would be extremely helpful. All response I get is that logcat isn't in /sbin/sh. I tried adding it to a separate /sbin/sh folder in my test build, but no dice
Good news is I found out the MSM8225 chipset was designed to be fully backward compatible, both hardware and software, with the MSM7225A and MSM7227A phones, of which Qualcomm sold about a 100 million. So, I've begun studying the device and vendor trees for the HTC Explorer (Pico), which is a MSM7225A model. Important because it has the compatible 7225A chipset and uses the ARMv7 cpu instruction set - which is the same as the Desire X.
We'll keep you guys posted, also when we need testers. :good:
Ours is cortex a5, that's why it is compatible with msm7227. But the not booting issue is probably due to some thing missing or wrong in device.mk. the board config is ok. And kernel source is also available on htcdev and git simonsimons23. The device tree and vendor mk files need correction. At least that's my thinking.
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Ours is cortex a5, that's why it is compatible with msm7227. But the not booting issue is probably due to some thing missing or wrong in device.mk. the board config is ok. And kernel source is also available on htcdev and git simonsimons23. The device tree and vendor mk files need correction. At least that's my thinking.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
OK, I'll leave the boardconfig for now (am checking the files alphabetically) and move on to device.mk If I see anything I don't get or differs from the pico source (has official CM9), I'll let you know here or through pm. I was thinking the same about the device and vendor trees, it's our starting point and we're stuck here already lol. I know about the githubs, I'll check the changes (if any) simonsimons made.
I was thinking though : don't we need the 1.18 kernel to do this ? I already flashed the updated kernel with the 1.18 ruu. I checked on htcdev and it only lists the 1.14 kernel source. Or is there a way to get it from a running phone ?
missing logcat....
Hi Guys,
I don't know why logcat is missing, but to obtain kernel messages you could run the "dmesg" command instead.
I would like to participate in DX porting. I got intermediate knowlegde in android, but I'm really good in linux and kernel stuff.
Are you guys hanging around in IRC somewhere so we cant talk directly?
currently I am compiling lloirs tree. It is running for some time already...
hang loose
maze
atmel-touchscreen.kl is not in any git
Hi Guys,
I still try building the stuff, but atmel-touchscreen seems to be missing so I decided to remove it from
htc/protou/device_protou.mk. Now it continues compiling ....
( device/htc/protou/prebuilt/usr/keylayout/atmel-touchscreen.kl:system/usr/keylayout/atmel-touchscreen.kl)
Any progress OP??? I did a recent build with some mods on weekend but it failed to boot. I'm highly suspicious that its a kernel issue although i cant say for sure. If any one manages to boot it, even if its till the boot animation, DO POST AND SHARE, coz then its easier going forward.
Regards
neXus PRIME said:
Any progress OP??? I did a recent build with some mods on weekend but it failed to boot. I'm highly suspicious that its a kernel issue although i cant say for sure. If any one manages to boot it, even if its till the boot animation, DO POST AND SHARE, coz then its easier going forward.
Regards
Click to expand...
Click to collapse
got a logcat? or even a kmsg? you can get the kmsg by rebooting into TWRP mount system and open the file manager in advanced and going into /proc grab last_kmsg from in there, you can also find me on IRC Most days, (except tonight i'm working )
-Lloir
I'm sorry guys, haven't been able to do much for this project anymore...no time (holidays and starting training to become system administrator), not to mention I spilled coke all over my Macbook Pro
Lloir said:
got a logcat? or even a kmsg? you can get the kmsg by rebooting into TWRP mount system and open the file manager in advanced and going into /proc grab last_kmsg from in there, you can also find me on IRC Most days, (except tonight i'm working )
-Lloir
Click to expand...
Click to collapse
Doesnt even get past the splash screen (the one with HTC red letter sentence about private build). I used the prebuilt kernel which i have used in recovery. I'll try getting kmsg though.
Regards
neXus PRIME said:
Doesnt even get past the splash screen (the one with HTC red letter sentence about private build). I used the prebuilt kernel which i have used in recovery. I'll try getting kmsg though.
Regards
Click to expand...
Click to collapse
You can still logcat on that screen if adb sees it
Sent from my HTC One X+ using Tapatalk 2
nopes. I have QtADB running in background with logcat ON all the time. Thats how i can never miss if it gets to boot. But i didnt check kmsg though.
My laptop is in a mess right now and i have jellybean source synced by mistake over night. Now i gotta go back to ICS and it will again take a day to sync as the net is crappy here.
I got a ramdisk hack for you when I get home to enable very early adb. If I had the DX I would do it for you guys, but I'll help where I can. Don't be afraid to pm me if you need to.
Sent from my HTC One X+ using Tapatalk 2
Lloir said:
I got a ramdisk hack for you when I get home to enable very early adb. If I had the DX I would do it for you guys, but I'll help where I can. Don't be afraid to pm me if you need to.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Tell me, should I use pre built kernel or use HTC provided sources?
Must have unlocked bootloader and cwm installed.
So I wanted the 4.3 PACrom and was able toe port it. It wasn't too hard. I used antonx cm 10.2 as base and mateo1111 pacrom as port.
Everything works so far that I see. i just thought i would share. The WiFi is working on boot but I'm putting links to files in my dropbox if anyone wants to make this better. Thanks to everyone that made this possible.
Slimbean apps. http://db.tt/KUk1ug4e WiFi fix scripts. http://db.tt/Hq9GUcyk
(Old ROM link on 2nd page)
Okay so I updated the port and everything works great.
WiFi works without any scripts. No fc errors. No random reboots added leolawliet build prop and penderengine tweaks. runs great. This port is basically the same as mateo1111 all in one pacrom but made to use on p769
Minor fixes. Tweaks can be enabled or disabled in PAC settings init. Just like in mateo1111 all in one pacrom.other then that no other tweaks added.l9advanced settings app works. Surprisingly a lot smoother and faster and more stable then before no random reboots or any other problems so far.
updated rom link. 9/14/13 http://db.tt/rrUVfCND
updated rom link 9/28/13 https://db.tt/cMc3BfU7
updated rom link 9/29/13 https://db.tt/dIGIqJbN
Minor fixes
For tweaks check out @leolawliet thread
Everything's the same for installation. Wipe install ROM install gapps and reboot. No need to fix WiFi thanks to kuma82. WiFi is working on boot
All credit goes to ANTONX ,MATEO 1111 , AND KUMA82. And leolawliet.
SORRY FOR NOT MAKING THAT CLEAR.
twinnfamous said:
So I wanted the 4.3 PACrom and was able to port it. It wasn't too hard. I used antonx cm 10.2 as base and mateo1111 pacrom as port.
Everything works so far that I see. i just thought i would share. The WiFi needs to be fixed like the other PAC port but I'm putting links to files in my dropbox if anyone wants to make this better. Thanks to everyone that made this possible.
ROM link. http://db.tt/L4RkK4pC. Slimbean apps. http://db.tt/KUk1ug4e WiFi fix scripts. http://db.tt/Hq9GUcyk
Everything's the same for installation. Wipe install ROM install gapps reboot fix WiFi and reboot
Click to expand...
Click to collapse
I know you mean well but you can do a better job on giving credits
Plus you didn't even give me any credit for making those scripts. :what:
Actually, Lelus script is a lot cleaner to use.
Anyways, thanks for sharing.
CM 10.1 P769
twinnfamous said:
So I wanted the 4.3 PACrom and was able to port it. It wasn't too hard. I used antonx cm 10.2 as base and mateo1111 pacrom as port.
Everything works so far that I see. i just thought i would share. The WiFi needs to be fixed like the other PAC port but I'm putting links to files in my dropbox if anyone wants to make this better. Thanks to everyone that made this possible.
ROM link. .http://db.tt/L4RkK4pC Slimbean apps. http://db.tt/KUk1ug4e WiFi fix scripts. http://db.tt/Hq9GUcyk
Everything's the same for installation. Wipe install ROM install gapps reboot fix WiFi and reboot.
All credit goes to ANTONX ,MATEO 1111 , AND KUMA82.
SORRY FOR NOT MAKING THAT CLEAR.
Click to expand...
Click to collapse
maybe a couple of screenshots of it installed running??
elpuertorro said:
maybe a couple of screenshots of it installed running??
Click to expand...
Click to collapse
Here u go .
twinnfamous said:
Here u go .
Click to expand...
Click to collapse
Thank you sir!
Nice work, thank you for the port.
Sent from my LG-P769 using xda app-developers app
Should I release my port? It's not plain PACrom JB anymore, added my tweaks.
Sent from my LG-P769 using Tapatalk 2
leolawliet said:
Should I release my port? It's not plain PACrom JB anymore, added my tweaks.
Sent from my LG-P769 using Tapatalk 2
Click to expand...
Click to collapse
Yea I just did this for personal and thought I would share. I just got impatient I would love to try yours.
Wifi working on fresh install
What's up people, thanks to @Lelus and a couple of other xda members (@zeppelinrox & @dk_zero-cool), I modified Lelus script a little, and it's a init.d.
The think I like about @Lelus method is the Wi-Fi MAC address is a spoof (it's not your real MAC address)
This guyyy (Italian voice) @Lelus :highfive:
So you won't have to use the other scripts I made, unless you want your real Wi-Fi MAC address shown.
anyways, here is what the script looks like
#!/system/bin/sh
while [ ! "`ps | grep [a]ndroid`" ]; do sleep 10; done;
busybox sleep 30
if [ -e /data/misc/wifi/config ]; then
busybox mount -o remount,rw /system
busybox ifconfig wlan0 down
busybox rm /data/misc/wifi/config
busybox wifimac
busybox rm /system/etc/init.d/90kuma
exit 1
else
sh /system/etc/init.d/90kuma
fi
After the first boot, it's set to delete, so you won't ever see if you look in /etc/init.d
Anyone is welcome to include the script in your port
Since I'm a real nice guy, I uploaded the PAC 4.3 (ported by @twinnfamous) with the script included HERE
md5sum: 216cfd36237d3eb1fe7d444def082a9d
Note: I have not tried this on a dirty flash, soo... report your findings lol
ALL THANKS GO TO
@AntonX
@mateo1111
@Lelus
@twinnfamous & @leolawliet (for saving me the time on porting it LOL)
Last but definitely not least
Cyanogen Team
AOKP Team
Paranoid Android
PAC-man Team
Well for some reason WiFi just stopped working after a deep sleep, and rebooting it, did not help. I had to run the script again. It's a small price to pay for a spoofed Mac in my opinion. I really don't know what happened. I can turn it off/on and the WiFi sticks. Must have been a hiccup, I guess.
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Well for some reason WiFi just stopped working after a deep sleep, and rebooting it, did not help. I had to run the script again. It's a small price to pay for a spoofed Mac in my opinion. I really don't know what happened. I can turn it off and on the WiFi sticks. Must have been a hiccup, I guess.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
For some reason i think these phones on cm 10.1 and 2 and derived work have a deep sleep issue..i notice that while on cm if i press my mic on the BT headset to make a call it doesn't do anything..if i press power to wake then the BT signal even by passes the default lock screen as it should - on the tmo rom it wakes the phone and makes the call without me even have to touch the phone..so maybe that's something to look at in these phones with the cm rom..
elpuertorro said:
For some reason i think thsese phones on cm 10.1 and 2 and derived work have a deep sleep issue..i notice that while on cm if i press my mic on the BT headset to make a call it doesn't do anything..if i press power to wake then the BT signal even by passes the default lock screen as it should - on the tmo rom it wakes the phone and makes the call without me even have to touch the phone..so maybe that's something to look at in these phones with the cm rom..
Click to expand...
Click to collapse
Did you bring this to @AntonX or @mateo1111 attention?
Sent from my LG-P769 using Tapatalk 2
leolawliet said:
Did you bring this to @AntonX or @mateo1111 attention?
Sent from my LG-P769 using Tapatalk 2
Click to expand...
Click to collapse
Nope but will do now that you mention it thanks!
kuma82 said:
What's up people, thanks to @Lelus and a couple of other xda members (@zeppelinrox & @dk_zero-cool), I modified Lelus script a little, and it's a init.d.
The think I like about @Lelus method is the Wi-Fi MAC address is a spoof (it's not your real MAC address)
This guyyy (Italian voice) @Lelus :highfive:
So you won't have to use the other scripts I made, unless you want your real Wi-Fi MAC address shown.
anyways, here is what the script looks like
#!/system/bin/sh
while [ ! "`ps | grep [a]ndroid`" ]; do sleep 10; done;
busybox sleep 30
if [ -e /data/misc/wifi/config ]; then
busybox mount -o remount,rw /system
busybox ifconfig wlan0 down
busybox rm /data/misc/wifi/config
busybox wifimac
busybox rm /system/etc/init.d/90kuma
exit 1
else
sh /system/etc/init.d/90kuma
fi
After the first boot, it's set to delete, so you won't ever see if you look in /etc/init.d
Anyone is welcome to include the script in your port
Since I'm a real nice guy, I uploaded the PAC 4.3 (ported by @twinnfamous) with the script included HERE
md5sum: 216cfd36237d3eb1fe7d444def082a9d
Note: I have not tried this on a dirty flash, soo... report your findings lol
ALL THANKS GO TO
@AntonX
@mateo1111
@Lelus
@twinnfamous & @leolawliet (for saving me the time on porting it LOL)
Last but definitely not least
Cyanogen Team
AOKP Team
Paranoid Android
PAC-man Team
Click to expand...
Click to collapse
just remove the "remove" part of the script and it will apply it on each reboot.
Code:
busybox rm /system/etc/init.d/90kuma
now time to fix Hybrid Properties in 4.2.2
Kid_Ding said:
just remove the "remove" part of the script and it will apply it on each reboot.
Code:
busybox rm /system/etc/init.d/90kuma
now time to fix Hybrid Properties in 4.2.2
Click to expand...
Click to collapse
Yeah I thought it was a one time deal but, it stops working sometimes. Not sure why.
kuma82 said:
Yeah I thought it was a one time deal but, it stops working sometimes. Not sure why.
Click to expand...
Click to collapse
right, but at least you've made a semi-permanent fix. keeps wifi going without having to run terminal commands after a flash. after every reboot wifi is solid everytime. thanks again @kuma82
Kid_Ding said:
right, but at least you've made a semi-permanent fix. keeps wifi going without having to run terminal commands after a flash. after every reboot wifi is solid everytime. thanks again @kuma82
Click to expand...
Click to collapse
Thanks
Yeah, I had a lot of trial and errors before I was finally able to get it to work. I'm thinking I can lower the wait ttime, but I didn't want to put to much stress on the system at boot.
updated 4.3 pac
Here is link for updated port http://db.tt/DsLV6O7G
Updated base with antonx latest cm10.2 and added kuma82 script to init.d. So wifi works on first boot and every boot so far.
Seems alot smoother and faster and everything is working that I see. No random reboots even at 1350.
Big thanks to kuma82, antonx, lelus, mateo1111,and everyone else that helps make this possable.
pender engine works great
Pender engine and leolawliet build prop tweaks works great on this port. Here is link for pender engine. http://d-h.st/WKN
U can take out boot animation and no frills is not needed as overclocking options is built in settings performance app. Thanks again leolawliet
Your work is great.
I'm crossing my fingers and hoping that I can get this working on my phone. I'm so tired of stock firmware.
Sent from my LG-P769 using XDA Premium 4 mobile app