yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] kagedws6:
I'm guessing the recovery needs to have the ramdisk set like the bootimg does.

where as I don't have the ablity to do that at work I had both the newest recoveries built using the CWM builder (touch and non touch recoveries) can someone take a look to see if they can possibly unpack and repack them so we can use them?

I also let koush (threw twitter) know since the uncorrected one is currently able to download threw rom manager

**Both were created using http://builder.clockworkmod.com/ and I had uploaded the original recovery attn1 had made*

http://dl.dropbox.com/u/93738392/recovery08292012.img

http://dl.dropbox.com/u/93738392/recoverytouch08292012.img

Both have file sizes ~6mb but the stock and the one attn1 made were about ~10mb

Below is the info we had to add the correct padding to the bootimg. not sure if this applies to the recovery as well

**Thank you jcase for figuring this out and thank you attn1 for figuring out an easy way for us mortals to do it! And also IOMonster**

./mkbootimg --kernel kernel --ramdisk boot.img-ramdisk.gz --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom loglevel=0' --board presto --base 0x40200000 --ramdiskaddr 0x41400000 --output boot.img

dd if=/dev/zero of=boot.img bs=4096 count=1 oflag=append conv=notrunc
[Miscellaneous Android Development] kagedws6:
**Edit doublepost**
[Miscellaneous Android Development] stevotdo:
I installed the one through rom manager. I'm not sure if is a fixed version or not. I do know the recovery.img is not very picky about the way everything is packaged.
[Miscellaneous Android Development] davepmer:
I do believe that the pdl flashes the bootloader. Think that is what happened to the ones that got bricked. Yes there is an emergency mode by pressing vol up and down, I have not tried to see if fastboot works there or not. Since recovery has it's own kernel it is kind of hard to mess it up by just flashing the system and the boot kernel.
[Miscellaneous Android Development] kagedws6:
if you reboot to recovery u'll see the version is still the older one. and when I manually tried to flash it threw fastboot it rejected it

I went to go mess with it last night and aparently I need to buy a new hard drive for my desktop....fun stuff
[Miscellaneous Android Development] kagedws6:
I'm searching with no luck so far but I did post your post here to see if we could get any help from anyone over at that site as well
[Miscellaneous Android Development] mifl:
Three questions:

What version of android is installed on your device?

What kernel version do you use?

Do you have a repository where I can see what you have done?

Greetings.

PS

: open a thread for your device, this is for the Pantech Burst.
[Miscellaneous Android Development] Leechoonhwee:
1. 4.1.2 is the version installed

2. I am trying to use 4.2.2 kernel from Sony => https://github.com/drewx2/android_kernel_sony_apq8064.git

3. I am still in the midst of sorting things out but I am forking from

https://github.com/CyanogenMod/android_device_oppo_find5.git

I have already extracted most of the files for the vendor part and now I am seeing what I can do with the kernel.

I started a thread on this but because I needed some help hence I am asking here.

Thanks
[Miscellaneous Android Development] mr72:
SIM problem with CM10

I am cross-posting this from the devsnest forum, mostly because I really need help quick.

First of all, I think this is a radio or baseband issue, but I am not 100% sure. I also have a sense this is a CM10 software/config issue, and I am quite confident this is NOT a hardware issue.

History:

several times throughout 2012 I took my AT&T Burst, with rooted/stock GB and ICS, with me from the USA to other countries including S. Korea, China, Finland, France, Italy, Germany, Switzerland, Denmark, and probably a dozen others I forgot to mention. It worked fine.

This time, I went to England, Germany and now Italy (going to the Netherlands tomorrow), and this is the first time with CM10.

In short, the phone doesn't work.

There is no signal (empty triangle icon instead of signal bars) and when I do Settings -> Mobile Networks -> Network Operators -> Choose automatically I get "Your SIM doesn't allow a connection to this network".

Further, in Settings -> About phone -> Status it shows:

Network: Unknown

Mobile network type: UNKNOWN:0

Service state: Out of service

Roaming: Not roaming

Mobile network state: Disconnected

Serial number: unknown

And in Settings -> About Phone it shows Baseband version: Unknown

However it has my phone number, IMEI, etc. and is reading the SIM correctly according to my SIM reading app.

I have rebooted many times, factory reset many times, re-flashed CM10 many times (the 4/21 build), wiped cache/dalvik many times. I even restored my pre-CM10 rooted stock ICS (which worked in February when I was in Berlin for 2 weeks) and it now doesn't work. I even went so far as to reformat the data, cache and system partitions in hopes that whatever it broke would be wiped. The only thing I haven't tried is restoring the original PDL, or reinstalling the JUUS09032012.zip factory ICS. I am currently downloading that now but there are 5 hours left and I am sure I will be on my way back to the USA before I get a chance to try it.

Everything indicates that the CM10 installation has somehow busted the radio or baseband has been broken, and it is not being fixed by restoring the backup from pre-CM10.

The thing is, I can't reproduce this problem in the USA, but I am coming back here for a family vacation at the end of May (France) and I seriously need my phone to work. I have the rest of the day and part of the day tomorrow to try and make this work while in the hotel here.

Anyone know what's going on? I really do need some urgent help making this work.
[Miscellaneous Android Development] mrakattack:
FYI - important

Do not use koush's superuser app, caused kernel panic for me when trying to use GermainZ buttonled app

Sent from my PantechP9070 using cm10 042113
[Miscellaneous Android Development] mrakattack:
Turned off phone to charge, came back to check got a kernel panic "apq modem crash" on top of the battery charging splash, should I be worried?

Sent from my PantechP9070 using cm10 042113
[Miscellaneous Android Development] mr72:
FYI, I posted over in the devsnest forums, which has gotten little more response than here:

http://www.devsnest.com/phpbb/viewtopic.php?f=12&t=142&p=850#p850

The summary is that it appears that somehow CM10 breaks something in the radio or SIM settings that is not repaired by restoring a backup. Whatever it breaks affects usability outside of the USA (specifically in Europe, tried it in 5 countries now).

So once you flash CM10, if you have to use the phone in Europe, your only choice currently is to return the phone to stock by downgrading to the official Pantech PDL using the Pantech upgrade tool in WIndows.

This is very unfortunate since CM10 is very appealing and besides this was working very well on this phone, particularly with better battery life than stock ICS and far faster, less laggy, fewer bugs, and of course not inhibited by the Pantech lock screen, dialer, etc. which are really bad from a usability standpoint. I am hopeful that someone will fix this problem but in truth, I am not optimistic, since it probably doesn't affect most users. But for me, since I travel to Europe regularly, it makes the phone unusable.

Now I am officially on the hunt for another phone with similar hardware spec, 4" screen, LTE/GSM/WCDMA/HDSPA+, but that is officially supported by Cyanogenmod so that it is unlikely to run into this issue. For a couple of weeks there I thought the Burst was the perfect phone, and with CM10 it really was until I found myself traveling again.
[Miscellaneous Android Development] herecomesmaggi:
So sad to hear that. But in India handset works perfectly. Since very less people suffer this so I also wouldn't say to stay optimistic but wait for it may be your call gets to the Dev and Need might be sufficed....

If I were u, I create two nandroid backups 1 for Stock and other for CM10. You can swap them from cwm in almost 1 min :D:D
[Miscellaneous Android Development] mifl:
New kernel versión

After much work, I have merge the branch "caf/jb_mr1_chocolate" with our kernel.

Lack clean some proprietary tags introduced by Pantech, but compiles without errors.

It is available here: https://github.com/mifl/android_kernel_pantech_presto/tree/cm-10.1/

Greetings.
[Miscellaneous Android Development] mrakattack:
So now I can compile cm10.1? Lol
[Miscellaneous Android Development] xxthe:
You can try I suppose.
[Miscellaneous Android Development] mrakattack:
I'm just kidding, I leave it to the pros ;)
[Miscellaneous Android Development] mr72:
That would be great except that restoring the stock backup after going to CM10 does not resolve the problem that CM10 creates, so you must go all the way back and downgrade the phone to completely stock, redo root, etc. using the Pantech tools and the original PDL.

I would love it if it were that simple, just use two backups.
[Miscellaneous Android Development] omdhar:
I too have been moving between ICS stock and cm10 for over two months now without hassle.

Sent from my PantechP9070
[Miscellaneous Android Development] roambekar:
Do i need to unlock the phone again aft going back to flash by pdl tool..? If yes then is that unlock code calculator provided on gizmo forum working?
[Miscellaneous Android Development] herecomesmaggi:
U don't have to use unlock tool again and again but In case unlock code is requested then tool provides the correct code. (Tested and verified by me)

Regards
[Miscellaneous Android Development] mrakattack:
How do I pull the git for just the kernel to try and build cm10.1? Lol
[Miscellaneous Android Development] omdhar:
Hmm. No sound or update from our cm10 developers for while. Is current build final or can we expect further update. Issue like graphics and WiFi tether still require fix.

Sent from my PantechP9070
[Miscellaneous Android Development] mrakattack:
Compiling CM10.1 right now, no errors so far

spoke too soon

make: *** No rule to make target `/home/mrakuuls/android/cyanogenmod/jellybean/out/target/product/presto/obj/lib/libnv.so', needed by `/home/mrakuuls/android/cyanogenmod/jellybean/out/target/product/presto/obj/EXECUTABLES/hwaddrs_intermediates/LINKED/hwaddrs'. Stop.
[Miscellaneous Android Development] mifl:
First you have to adapt the boot files. Compiling is possible, but the jellybean boot files are not the same.
[Miscellaneous Android Development] mrakattack:
do i even dare ask how to do that? lol
[Miscellaneous Android Development] mr72:
Did you read about the problem that I was having? This will work fine as long as you don't need to use the phone in some locale (like all of Europe) where CM10 has broken the radio. But once you install CM10 the damage is done and can't be undone without a complete return to stock as far as I can tell.
[Miscellaneous Android Development] pratyush997:
^ Buddy, I don't think that you will get network worldwide!
[Miscellaneous Android Development] hawkwind212:
Question, if for some reason I need to go back to the stock ICS (can't imagine why I will want to, but just in case), can I flash the ROM with the newest cwm touch? Or do I have to use s/w mode and Pantech tool? I remember trying it once going from cm10 back to davempr's deodex, and the result was a soft brick phone. Has anyone done it with cwm touch, flash the stock ics ROM from cm10? How do I go back to the version 5 of cwm if I have to, any ideas?

Sent from my Pantech P9070

on cm10 using Tapatalk 2
[Miscellaneous Android Development] kagedws6:
mr72 stated if he flashes back to stock via pdl the radio is fixed in the areas he is testing. but the moment cm10 is installed, even if he has a backup of stock or rooted ICS, the radio no longer allows network connection in European countries.
[Miscellaneous Android Development] kagedws6:
If you need to go back to stock use the stock PDL tool to make sure all existing traces of the changes made in CM10 are removed (with the exception of the storage area)
[Miscellaneous Android Development] pratyush997:
Doesn't seem like a bug

Burst rocking AOKP Tapatalk'd it.
[Miscellaneous Android Development] kagedws6:
installing cm\aokp\pa is somehow changing the way our radio works effectively breaking it for some countries. I would call that a bug. it might be more indepth then that as well we just haven't seen how its affecting us that are able to use it daily.
[Miscellaneous Android Development] mr72:
Wow!

Burst works fine stock, completely doesn't work as a phone once CM10 is added... and that's not a bug?

Trust me, it's a bug.

---------- Post added at 11:24 PM ---------- Previous post was at 10:54 PM ----------

BTW even in the USA Baseband is reported as "Unknown" so I think the radio is busted in USA and other places where it works with CM10, but just not in a way that prevents it from actually connecting.

It most likely has to do with some subscription if I had to guess. If I weren't completely swamped between now and when I have to go to Europe next I might actually look into it myself and see if I can find the problem. But I won't have time to come up for air until June, and hopefully someone more knowledgeable will have fixed it by then.
[Miscellaneous Android Development] pratyush997:
So, it's bug.

Burst rocking AOKP Tapatalk'd it.
[Miscellaneous Android Development] hawkwind212:
Thoughts about the baseband

After mr72's mentioned of Pantech burst running on CM10 based ROM having the basedband displayed as unknown. I did a little bit more research and found that supposedly most of custom ROMs do not include baseband firmware in the image. In order to have the baseband that fits our phone, we need to flash the phone with baseband firmware. There are many articles on XDA about flashing baseband ROM, it suppose to improve battery life and improve the communication. My question is where do we find baseband firmware for pantech burst? Don't suppose Pantechusa will provide them. Tell the truth that I never care about the baseband issue until mr73 mention it. There are many issues regarding CM10 for burst I rather seen fix first, and it seems many other custom ROMs for other phones all have their baseband display as unknown. Anyway, just want to chip in my couple of cents on issue of baseband.
[Miscellaneous Android Development] mr72:
FWIW I don't have any evidence that this is definitely related to the problem I was having. It may be just a coincidence.
[Miscellaneous Android Development] chevanater:
When I flash the rom and reboot it stays at the CM10 splash screen forever? I tried wiping and everything before flashing and still nothing. Any help is greatly appreciated!
[Miscellaneous Android Development] jellybean59:
On 1st reboot it will take a while but after 1st reboot is completed it should boot normally next time you reboot.
[Miscellaneous Android Development] ninjah:
FAB2200

this is our HP/SP amp

http://www.fairchildsemi.com/ds/FA/FAB2200.pdf

This is our Audience chip(no datasheet yet)

http://www.audience.com/pdf/Audience_eS310.pdf
[Miscellaneous Android Development] davepmer:
Try this, boot up in cm10, make sure the phone can not connect to the network. Then flashing

http://www.4shared.com/zip/KIASoK2I/JUUS06252012-revert-from-ics.html

See if that restores the radio... It should be nearly the same as doing the factory PDL file. It flashes all the radio partitions back just like the PDL file does.

If that works, it maybe a link to one of the partitions that is getting lost
[Miscellaneous Android Development] mr72:
Thanks for the info Dave. Perhaps next time I'm in Europe with a weekend on my hands, I'll give this a try.

Unfortunately since I have to rely on my phone, I can't run CM10 normally especially when going to Europe.
[Miscellaneous Android Development] jenyayah:
In my case (after flashing on stock 4.0.4) it shows CM circle forever.

did you succeed ?

---------- Post added at 07:31 PM ---------- Previous post was at 07:06 PM ----------

Factory reset should be performed before flashing!
[Miscellaneous Android Development] jellybean59:
If you get back to recovery I would start over.

1. Reset

2. Wipe cache

3. Wipe dalvik

4. Format system

5. Install ROM

6. Install gapps

7. Reboot

I would also recommend downloading latest build.
[Miscellaneous Android Development] robobub:
There isn't fastboot or anything for this device for unbricking?
[Miscellaneous Android Development] hawkwind212:
How are you going to get fastboot when the only driver that the computer will recognize is "qhsusb_dload?" You need

the android driver for the phone to communicate with sdk tools. The only driver you got in that bricked phone is Qualcomm's driver.
[Miscellaneous Android Development] davepmer:
Thanks

I know where the problem lies I just can't figure put a way to fix it. The problem starts with libcamera.so. so far I have had to use our OEM version. But to take care of all the links embedded in it I have to use our OEM libandroid_runtime.so.
[Miscellaneous Android Development] PantechBurstOwner:
So what exactly are you trying to do dave? I'm guessing you're the one working on the ROM, could you tell me what it is that is giving you that error and what action you're performing to cause it? Lol sounded formal but didn't know how to word it

Sent from my PantechP9070 using Xparent Cyan Tapatalk 2
[Miscellaneous Android Development] davepmer:
Well I really hope I am not the only one working on a rom. I am trying to start simple least I thought it would be. I am trying to compile a cyanogenmod 7 rom. What's giving me trouble is the cm source code requires I use libaudio.so and libcamera.so but the presto versions have dependencies that I can only meet by adding the OEM presto libandroid_runtime.so. once I add that I get this can not find decl error. I searched all the presto files and the missing decl is only mentioned in the oem libandroid_runtime.so no where else. It is also not in the libandroid_runtime of any similar phone.
[Miscellaneous Android Development] stevotdo:
I've been busy all week. Still working on it, would you mind uploading your current device and vendor folders again.

That way as soon as I get time we can be on the same page.
[Miscellaneous Android Development] PantechBurstOwner:
The error on the previous page has to do with Landroid, not the packaging of the rom. I'm not familiar with what LanDroid is but it seems like an app that has to do with managing system files?

Sent from my PantechP9070 using Xparent Cyan Tapatalk 2
[Miscellaneous Android Development] davepmer:
http://www.4shared.com/archive/ZQB1woKk/device.html

This should get you where I am now as well as a few of the past tries. If there was just a way to compile all the .so files instead of using some from the presto.
[Miscellaneous Android Development] :
Where is the samsung_oled video driver located in the presto_kernel source from Pantech?

Here is my output for the driver files:

~/android/kernel/presto_kernel /drivers $ ls

accessibility cpufreq hwmon Makefile oprofile s390 telephony

acpi cpuidle i2c mca parisc sbus thermal

amba crypto ide md parport scsi uio

ata dca idle media pci serial usb

atm dio ieee1394 memstick pcmcia sfi uwb

auxdisplay dma ieee802154 message platform sh vhost

base edac infiniband mfd pnp sn video

block eisa input misc power spi virtio

bluetooth firewire isdn mmc pps ssb vlynq

cdrom firmware Kconfig mtd ps3 staging w1

char gpio leds net rapidio switch watchdog

clocksource gpu lguest nubus regulator tc xen

connector hid macintosh of rtc tdmb zorro

Do you have the filename in question?
[Miscellaneous Android Development] kagedws6:
"auxdisplay dma ieee802154 message platform sh vhost" looks promising maybe?
[Miscellaneous Android Development] davepmer:
Believe it is in drivers/video/msm/

Not at my computer right now. But in most the kernel source codes it is missing.

Don't forget the touch screen driver qt602240_ts in is in drivers/input/touchscreen/ but it is normally missing too.
[Miscellaneous Android Development] :
I see lcdc_Samsung_oled_pt.c in the msm folder. Also found qt602240_ts.c

Thank you. Looking at them now. If I can't figure it out I have many eager full sail students close by.
[Miscellaneous Android Development] davepmer:
well if you have many eager students have them look at this, it is devices-msm8x60.c from msm-3.4 kernel. I keep getting /home/dave/android/kernel/msm/msm/arch/arm/mach-msm/devices-msm8x60.c:2314: error: variable 'vidc_platform_data' has initializer but incomplete type

/home/dave/android/kernel/msm/msm/arch/arm/mach-msm/devices-msm8x60.c:2316: error: unknown field 'vidc_bus_client_pdata' specified in initializer

/home/dave/android/kernel/msm/msm/arch/arm/mach-msm/devices-msm8x60.c:2316: warning: excess elements in struct initializer

error, forbidden warning: devices-msm8x60.c:2316

fyi the source code is from https://www.codeaurora.org/gitweb/quic/meego/?p=kernel/msm.git;a=summary warn you it is missing a lot of make files, none seem to be anywhere to change what is happening. I used the make files from android 3.4 kernel to fill in the missing ones. to save time I attached arch/arm/mach-msm/devices-msm8x60.c

not sure why but every time I git a source code it seems to have a lot wrong with it.
[Miscellaneous Android Development] davepmer:
Could someone out there givew a clue how to fix this error

LD arch/arm/mach-msm/built-in.o

arch/arm/mach-msm/socinfo.o: In function `smem_alloc':

/home/dave/android/kernel/msm/arch/arm/mach-msm/smd_private.h:83: multiple definition of `smem_alloc'

arch/arm/mach-msm/proc_comm.o:/home/dave/android/kernel/msm/arch/arm/mach-msm/smd_private.h:83: first defined here

make[2]: *** [arch/arm/mach-msm/built-in.o] Error 1

make[1]: *** [arch/arm/mach-msm] Error 2

Compile fails it claims because smem_alloc is defined twice. it then tells the location line 83 of smd_private.h, it then tells me the first place that smem_alloc was defined, in line 83 of smd_private.h yes you got it the same place.
[Miscellaneous Android Development] davepmer:
bad when you answer your own question, you simply delete the definition.

---------- Post added at 09:54 PM ---------- Previous post was at 09:49 PM ----------

Have a new problem, will need help from the group on this one. The kernel compiles, but it has undefined referances in the linker. Not really sure how to fix as I have never run into this error.
[Miscellaneous Android Development] :
I posted this question in another forum, and was told:

" Read up on C and how to handle multiple declarations."

Well, I did some of the leg work and found some useful links which I am researching. For your convenience, I will post them here.

http://stackoverflow.com/questions/704995/c-multiple-declaration-of-function-error-when-linking

http://www.cplusplus.com/forum/unices/5784/

http://www.velocityreviews.com/foru...esent-inboth-libs-without-modifying-libs.html
[Miscellaneous Android Development] :
This is the other thread I was referring to:

http://xdaforums.com/showthread.php?t=1748297
[Miscellaneous Android Development] kagedws6:
I need to go back and reinstall ubuntu because even with the guides walking you threw how to's in 12.04 I'm still failing. gotta find an iso for 10 or 11 at the latest because it seems like there are more guides for 10 then anything else