Database Info

[ROM] [G1/MAGIC] 14/OCT/09 Android 1.6 AKIRAH "Phoenix" 3.1 - BFS303 memory patch

[ROM] [G1/MAGIC] 14/OCT/09 Android 1.6 AKIRAH "Phoenix" 3.1 - BFS303 memory patch
Back from ashes...
This is official android 1.6 release for ADP1 + some AOSP, rooted and modified.
Current version
HTML:
3.1
* Fixed data synchronization
* Better terminal instead of terminal.apk
* WIFI Tether 1.6pre3
* More languages
* Camera should be fixed
* IM is back
* comes with ROM Updater
Suggest to wipe ext, and wipe data. You know the rules, might not be really required, but expect some FC's and problems.
Known issues
HTML:
[I]No T-Mobile IM[/I]
Past versions
HTML:
3.0.2a Comes with BFS-303 + memory patch kernel (107 Mb RAM)
* most of problems should be fixed now
* Terminal, Wifi-Tether 1.6pre3
[ problems: no data synchronization, gmail push broken ]
3.0.1
kernel 2.6.29-mkk5 BFS 303
Japanese keyboard fixed
New cyanogen init.d
Cyanogen phone.apk and mms.apk
3.0
- updated frameworks and apks from official framework and SDK.
- Supported languages: Czech, German, English, Spanish, French, Italian, Japanese, Korean, Dutch, Polish, Russian
- added some parts of text to speech and accessibility
- Full package update (no wipe required)
I suggest to cleanup /system/sd/dalvik-cache (might work without, but it's better to do that).
2.1 - upgraded kernel to 2.6.29.6-bfs300-mkk2
see 2.0
2.0 - apps2sd
cm kernel 2.6.29 from 4.1.11.1
all donut goodies
compcache enabled by default
terminal, pdfreader, htc ime, and few things that I've forget to mention
What it requires:
HTML:
root
Radio 2.22.19_26I
Sdcard with FAT32/EXT2 or EXT3 or EXT4/
Recovery image that can flash ROMS not signed with release-keys
DangerSPL / HaykuroSPL
Installation
HTML:
Backup
Wipe
* You might need to format your linux partition
Flash
Downloads
Akirah 3.1
ANDROID1.6 Akirah.3.0
Upgrade from 2.0 to 2.1
ANDROID1.6 Akirah.2.1
ANDROID1.6 Akirah.2.0
Click to expand...
Click to collapse
Themes
Blackened by jonnybueno
Chimera by d750
Minus theme by david1171 for v.2x
Blur theme by Brandenk - for v2.x
Click to expand...
Click to collapse
Theme template by david1171
Click to expand...
Click to collapse

Thank you for reposting, it was locked to me too! flashing later today...

I might try this later, seems okay

akirah said:
What it requires:
root
Radio 2.22.19_26I
Sdcard with FAT32/EXT2 or EXT3 or EXT4/
Recovery image that can flash ROMS not signed with release-keys
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is the sdcard partition really required or is it only required if one wishes to use the A2SD?
And does the Cyanogenized 1.4 Recovery image count here?

I have a feeling they are going to lock this one too, probably because the Google Apps are included.

So they should close all HERO and Rogers and almost all others.

If they lock this one, then someone high up at xda needs to write a clear policy about what is and isn't allowed on this site, Rom-wise. At the moment I'm sure its individal mods acting alone, each with differing interpretations of what the current site policy is.
If this Rom gets grief, I assume the same standards will apply to Hero roms? Have they closed down the theme boards yet? The problem is (in my view) is that there are far too many mods with itchy trigger fingers (see the raspberry link at the bottom of the first post in my BetterBrowser thread in my sig for a prime example)
Cyanogen is the subject of a cease and desist. Akirah isn't, neither is xda as a site. As long as the files are offsite thus ensuring xda isn't liable, why are different standards being applied here versus the WinMo boards?

have flashed and have no complaints, it zoom zoom super fast!!, everything seems to work have just installed advanced launcher.

Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/

akirah said:
Installation
HTML:
Backup
Wipe
erase dalvik-cache
You might need to format your linux partition
Click to expand...
Click to collapse
Where is the step in which you actually flash?

Downloaded before google SHUTS YOU DOWN SON

pinetreehater said:
Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/
Click to expand...
Click to collapse
same exact results here..

sstang2006 said:
same exact results here..
Click to expand...
Click to collapse
Try moving app app-private to some folder on /system/sd
and see if it helps

also blankscreen after trying update from 4.1.1.1

can i see some screen shot of this? D;
tnx!

pinetreehater said:
Coming from Cyanogens latest experimental build, the install blackscreened me. Wiped, cleared cache, and installed. Reflashed with the same result. I would love to watch what is happening with the adb tools, but that hasn't worked since I installed win7/
Click to expand...
Click to collapse
Use the latest drivers from the 1.6 SDK, works fine for me on win7.

makethetick said:
Use the latest drivers from the 1.6 SDK, works fine for me on win7.
Click to expand...
Click to collapse
Same results here. Using Win7 x64 and it's worked perfect from day 1, but I started with the updated drivers.

Don't hate Google just yet
kreat1ve said:
Downloaded before Google SHUTS YOU DOWN SON
Click to expand...
Click to collapse
I'm not sure, but I think, the reason Cyanogen received a C&D is because he has an application on the android market that is open to the public that distributes Google copyright applications exclusive to those only on Google experience phones such as the G1. This website is for developers, and it sucks that this website has become more of a popularity contest than what it is meant to do, which Google promotes, the developing part of it. Being that Android is for everyone and can be accessed from non-Google experience phones, that is why he was ordered to stop before legal action is taken. If they were smart, they would have waited until Cyanogen became rich and then sued him for millions for copyright infringement, HOWEVER, they do believe in open-source projects such as Android. Google sells there brand in different packages, if you want the Google brand it will cost you more. They want to take down Microsoft down as much as all of us do. So I wouldn't hate them just yet, they still believe in something good.
Yes this is off-topic, felt i should actually post on an off topic post already. thnx

I adb pulled system/sd/*
then formatted ext, wiped and flashed rom no problems.
I then used adb file explorer to bulk install app-private and app back to phone.
from previous thread it seemd people had the black screen when trying to update straight from 4.1.11.1 so decided formatting ext is best bet

+1 for black screen. Wipe and delete dalvik-cache.
D/dalvikvm( 2520): GC freed 8907 objects / 492664 bytes in 142ms
E/System ( 2520): Failure starting core service
E/System ( 2520): java.lang.NullPointerException
E/System ( 2520): at com.android.server.PackageManagerService.scanPackageL
I(PackageManagerService.java:1875)
E/System ( 2520): at com.android.server.PackageManagerService.scanDirLI(Pa
ckageManagerService.java:1771)
E/System ( 2520): at com.android.server.PackageManagerService.<init>(Packa
geManagerService.java:497)
E/System ( 2520): at com.android.server.PackageManagerService.main(Package
ManagerService.java:266)
E/System ( 2520): at com.android.server.ServerThread.run(SystemServer.java
:112)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting Status Bar Service.
E/SystemServer( 2520): Failure starting StatusBarService
E/SystemServer( 2520): java.lang.NullPointerException
E/SystemServer( 2520): at com.android.server.status.StatusBarIcon.getIcon(Statu
sBarIcon.java:143)
E/SystemServer( 2520): at com.android.server.status.StatusBarIcon.<init>(Status
BarIcon.java:65)
E/SystemServer( 2520): at com.android.server.status.StatusBarService.makeStatus
BarView(StatusBarService.java:306)
E/SystemServer( 2520): at com.android.server.status.StatusBarService.<init>(Sta
tusBarService.java:237)
E/SystemServer( 2520): at com.android.server.ServerThread.run(SystemServer.java
:194)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting Clipboard Service.
I/SystemServer( 2520): Starting Input Method Service.
E/SystemServer( 2520): Failure starting Input Manager Service
E/SystemServer( 2520): java.lang.NullPointerException
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiverIntern
al(ApplicationContext.java:782)
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiver(Appli
cationContext.java:757)
E/SystemServer( 2520): at android.app.ApplicationContext.registerReceiver(Appli
cationContext.java:751)
E/SystemServer( 2520): at com.android.server.InputMethodManagerService.<init>(I
nputMethodManagerService.java:437)
E/SystemServer( 2520): at com.android.server.ServerThread.run(SystemServer.java
:209)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/SystemServer( 2520): Starting NetStat Service.
I/SystemServer( 2520): Starting Connectivity Service.
W/dalvikvm( 2520): threadid=25: thread exiting with uncaught exception (group=0x
4001da68)
E/AndroidRuntime( 2520): Uncaught handler: thread ConnectivityThread exiting due
to uncaught exception
E/AndroidRuntime( 2520): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 2520): java.lang.NullPointerException
E/AndroidRuntime( 2520): at android.app.ActivityThread.getProvider(Activi
tyThread.java:3938)
E/AndroidRuntime( 2520): at android.app.ActivityThread.acquireProvider(Ac
tivityThread.java:3967)
E/AndroidRuntime( 2520): at android.app.ApplicationContext$ApplicationCon
tentResolver.acquireProvider(ApplicationContext.java:1514)
E/AndroidRuntime( 2520): at android.content.ContentResolver.acquireProvid
er(ContentResolver.java:579)
E/AndroidRuntime( 2520): at android.content.ContentResolver.query(Content
Resolver.java:147)
E/AndroidRuntime( 2520): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:472)
E/AndroidRuntime( 2520): at android.provider.Settings$Secure.getString(Se
ttings.java:1649)
E/AndroidRuntime( 2520): at android.provider.Settings$Secure.getInt(Setti
ngs.java:1689)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.getPer
sistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:123)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:47)
E/AndroidRuntime( 2520): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:87)
E/AndroidRuntime( 2520): Crash logging skipped, no checkin service
I/Process ( 2520): Sending signal. PID: 2520 SIG: 9
I/Zygote ( 2519): Exit zygote because system server (2520) has terminated
E/installd( 2361): eof
E/installd( 2361): failed to read size
I/installd( 2361): closing connection
I/ServiceManager( 2354): service 'batteryinfo' died
I/ServiceManager( 2354): service 'usagestats' died
I/ServiceManager( 2354): service 'telephony.registry' died
I/ServiceManager( 2354): service 'SurfaceFlinger' died
I/ServiceManager( 2354): service 'entropy' died
I/ServiceManager( 2354): service 'power' died
I/ServiceManager( 2354): service 'clipboard' died
I/ServiceManager( 2354): service 'netstat' died
D/AndroidRuntime( 2534):
D/AndroidRuntime( 2534): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 2534): CheckJNI is OFF
D/AndroidRuntime( 2534): --- registering native functions ---
I/Zygote ( 2534): Preloading classes...
D/dalvikvm( 2534): GC freed 800 objects / 44048 bytes in 7ms
D/dalvikvm( 2534): GC freed 240 objects / 13920 bytes in 6ms
D/dalvikvm( 2534): GC freed 228 objects / 14392 bytes in 7ms
Click to expand...
Click to collapse
Thanks.
BR.

Need help, Infinite Boot Loop, LG EVE (GW620)

My EVE seems to does this every couple days and then I have to wipe everything of the phone using "Fastboot -w". But I'd like to figure out why this is happening so I'm starting to log stuff using logcat through adb.
Here is what I think may be the issue but you tell me. I'm totally new to trying to debug this thing.
This is a series of Errors that occur when the android loop screen locks up and restarts the boot loop.
E/AndroidRuntime( 6118): java.lang.IllegalStateException: Cannot broadcast before boot completed
E/AndroidRuntime( 6118): at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:10389)
E/AndroidRuntime( 6118): at android.app.ApplicationContext.sendStickyBroadcast(ApplicationContext.java:930)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService.sendConnectedBroadcast(ConnectivityService.java:483)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService.handleConnect(ConnectivityService.java:568)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService.access$500(ConnectivityService.java:48)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService$MyHandler.handleMessage(ConnectivityService.java:714)
E/AndroidRuntime( 6118): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 6118): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 6118): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:91)
E/AndroidRuntime( 6118): Crash logging skipped, no checkin service
E/installd( 1067): eof
E/installd( 1067): failed to read size
E/appproc ( 6155): Can't open data/nv/command

Can you provide more of the logcat? Particularly what comes before the error. Or even make a file of the whole process and upload the file?
Also, does this happen with one particular ROM or have you tried various ROMs?

That isn't all for the errors though so maybe I should just post the whole log as a link to the file.
I hope someone has some idea about this cause reloading everything on the phone is getting tiresome.

I haven't really tryied that many other roms. I did try the new Rogers beta rom (V10G_00.kdz) but I think it still did it.
Here is one of two logs that I recorded at boot time. They look pretty much the same.
View attachment log.txt
Thanks for all your help.

Note in this next log the lgesystemd error at the end is another area where the android loop starts over.
View attachment Log1.txt

Could this be a currupt firmware seeing as how it seems like its an LG process freezing up?

[Q] Force close on ALL applications when keyboard input is requested

This one is fun - I'm getting an FC every time an application requests keyboard input. If I hit the Google search icon on the top left of the home screen, it immediately FCs - that's what I'm using to test.
I downloaded aLogCat to the device via Google Play on my desktop, and ran it. Here is what I believe to be the relevant log section , from tapping the search icon, to re-entering aLogCat.
I believe the ClipboardEx service is causing the issue, possibly as an interference with another app I have installed - but I don't know what, or how to give you guys a list of apps installed without just typing each one.
This issue happened once to me, and a factory restore fixed it - two weeks later, and it's back. I'm not an experience Android guy, though I am a nerd and a developer. Surely this is something fixable. Does anyone have any thoughts on what could be causing this?
Code:
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=1, s=]
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/ActivityManager( 184): START {intent.toShortString} from pid 383
D/PowerManagerService( 184): acquireDVFSLockLocked : type : DVFS_MIN_LIMIT frequency : 1008000 uid : 1000 pid : 184 tag : ActivityManager
W/ActivityManager( 184): mDVFSLock.acquire()
D/Launcher.HomeFragment( 383): onPause
D/Launcher( 383): onPause
V/TaskCloserActivity( 3234): TaskCloserActivity onReceive()
D/KeyguardViewMediator( 184): setHidden false
D/ActivityManager( 184): Trying to launch applicationName
D/ControlPanelRemoteService( 3246): onDestroy()
D/OpenGLRenderer( 383): Flushing caches (mode 1)
D/dalvikvm( 3157): GC_CONCURRENT freed 259K, 5% free 6784K/7111K, paused 2ms+3ms
D/KeyguardViewMediator( 184): setHidden false
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/libEGL ( 3157): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 3157): Enabling debug mode 0
E/ClipboardServiceEx( 3157): Had failed to obtaining clipboardEx service.
D/AndroidRuntime( 3157): Shutting down VM
W/dalvikvm( 3157): threadid=1: thread exiting with uncaught exception (group=0x40bb01f8)
E/AndroidRuntime( 3157): FATAL EXCEPTION: main
E/AndroidRuntime( 3157): java.lang.NullPointerException
E/AndroidRuntime( 3157): at android.sec.clipboard.ClipboardExManager.updateData(ClipboardExManager.java:241)
E/AndroidRuntime( 3157): at android.widget.EditText.onFocusChanged(EditText.java:134)
E/AndroidRuntime( 3157): at android.view.View.handleFocusGainInternal(View.java:3727)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5420)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2113)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5370)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1598)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2459)
E/AndroidRuntime( 3157): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3157): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3157): at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
E/AndroidRuntime( 3157): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 184): Force finishing activity com.google.android.googlequicksearchbox/.SearchActivity
E/android.os.Debug( 184): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
I/dumpstate( 3272): begin
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{423f3fe0 com.google.android.googlequicksearchbox/.SearchActivity}
W/PowerManagerService( 184): Timer 0x7->0x3|0x0
I/PowerManagerService( 184): Ulight 7->3|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 0
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/InputReader( 184): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.70 ]
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/PowerManagerService( 184): Ulight 3->7|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 140
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
D/VoldCmdListener( 89): asec list
D/VoldCmdListener( 89): CommandListener::AsecCmd::runCommand -> --
I/dumpstate( 3272): done
D/KeyguardViewMediator( 184): setHidden false
D/Launcher( 383): onResume
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/myTest ( 383): [MonthTheme] onResume!!
D/KeyguardViewMediator( 184): setHidden false
D/myTest ( 383): firstDayOfWeek = -1
I/power ( 184): *** release_dvfs_lock : lockType : 1
D/myTest ( 383): [MonthView] updateView.mStartDay: 1
D/DEFERED_APP_VISIBILITY( 184): tweaking closing app
D/PowerManagerService( 184): releaseDVFSLockLocked : all DVFS_MIN_LIMIT are released
W/ActivityManager( 184): mDVFSLock.release()
D/Launcher.HomeFragment( 383): onResume

I've now removed all downloaded applications from my Tab. No dice.
I'm going to see if I can dig up any more logs, then reset it I guess.

I've discovered that copying something to the clipboard also causes the FC. This is definitely an issue with TouchWiz's clipboard as far as I can figure out.

Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium

jamesd86 said:
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
It works for me, too, until the whole thing starts crashing, lol.
I reset to factory and re-installed all my stuff; it seems to be working now. I guess it's Samsung's way of reminding me to keep regular backups...

My tab crashed and then this same exact thing started happening. The logs mentioned ClipboardServiceEx.
I am rooted, so I started an adb shell and found that /data/clipboard has all the persistent clipboard entries (I love that feature by the way).
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
This fixed it, although it cleared all my "held" info in the clipboard. A small price to pay. If you really had to, you could probably fish in /data/oldclipboard for it. Of course, now I will go delete oldclipboard.
Hope that helps someone.

Thanks for that info, you never know!
Pp.
Transmitted from another galaxy with an Infected P-5113.

same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt

dorkmo said:
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
Click to expand...
Click to collapse
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.

wd5gnr said:
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
Click to expand...
Click to collapse
ok newbie here with samsung tabs having same problem, how do you boot into recovery and do an adb shell ? can see above how to clear the clipboard directory and i dont want to factory reset too hard to reload all the crap on ....
thanks

I had the same problem, I do not want to root my device, but I like to use the standard key board from Sumsung. I send a a-mail to a lot of dutch companies (resellers) to tell them about the problem. I think that Sansung must make a firware update to solve this problem. I what to ask all people who have problems with the keyboard to e-mail Samsung and there reseller to put preasure on Samsung to make a firmware.
I use a work a round, I use a 3e party keyboard untill Samsung makes a firmware update.

wd5gnr said:
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
Hope that helps someone.
Click to expand...
Click to collapse
YEZZZZZ THANK YOU VERY MUCH!!!:good::laugh:
This worked perfectly on my Samsung Galaxy Tab 2 10.1 (P5110)

Thanks wd5gnr for the solution, worked very well!
Regards.

Glad it helped. I noticed someone asked earlier for more details.
There are plenty of root tutorials here. As for installing ADB there are a few ways to go and it depends on your PC's OS and if you want to get someone's simplified package or not. Read: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and the comments on that page too. If you google something like "installing ADB" you should find lots of help.
Once you have adb installed and can get to a shell, you should be good with my earlier instructions.

Error on boot from logcat and freezing

This is the only exception that I see through logcat every time I run it and stop it after it freezes. I have tried fix permissions, dalvik wipe, and I don't want to wipe my phone. I don't have a recent nandroid, but in case I have to, are there any ideas on how I can backup my applications and the data without titanium backup? Should I just zip up the contents of /data and etc? I see that is apparently part of the android runtime. Any chance that this is malware?
[ 06-09 20:43:32.586 3581: 3581 E/AndroidRuntime ]
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to start receiver com.babelsdk.main.resources.BabelBootReceiver: java.lang.NullPointerException
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2287)
at android.app.ActivityThread.access$1600(ActivityThread.java:143)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1317)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4950)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1004)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:771)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at com.babelsdk.main.resources.BabelResources.scheduleSync(BabelResources.java:195)
at com.babelsdk.main.resources.BabelBootReceiver.onReceive(BabelBootReceiver.java:19)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2280)
... 10 more
Thanks.

Nevermind solved it.
It was Valet's app being stupid. Turns out this BabelBootReceiver was part of Valet.

[ROM][EOL][CARBON][KK 4.4.4] CarbonROM (MT4GS)

hLe Storm ROM 4.4.4
Looks like I graduated from ArchiKitchen, now compiling from source and I may be on to something here. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Now that that's out of the way, hLe Storm (pronounced "hailstorm") 4.4.4 is a build of CarbonROM, using the kernel from @Emmanuel U (among advice), and device identity and other projects from Team KitKatDS. As CarbonROM is EOL (end-of-life) as of April 5th (or earlier), some commits have been taken/"cherry picked" from CyanogenMod 11 source.
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WHAT WORKS:
Powers on
Phone calls
SMS and (after using the busybox trick) MMS
Mobile Data (HSPA detected with my carrier)
Wifi
Google Play
GPS, based on GPS Status & Toolbox
Camera via UCam app, also now stock and Google Camera
Torch
Needs further testing
WHAT DOES NOT WORK:
Camcorder in stock app records nothing
Probably the same for any replacement Camcorder app (encountered this problem earlier this month)
No detail in the Google Search bar with the default launcher (search and voice search still work, just need to tap blindly)
You tell me...
TODO:
Continue to extensively test current functionality.
Suggestions?
DOWNLOAD:
AndroidFileHost Mirror
CARBON-KK-UNOFFICIAL-20151213-2320-doubleshot.zip (MD5: 023864307a38b61d154e5679b229809b)
GAPPS:
OpenGapps Mini
OpenGapps Micro
OpenGapps Nano
INSTRUCTIONS:
Download ROM above, and your favourite GApps package
Save/push files to your External SD card (preferably in the root folder where you can find it later)
Reboot into recovery ("adb reboot recovery")
Nandroid/Back up device (optional)
Wipe cache and data/factory reset
Install ROM and GApps
Wipe Dalvik cache
Reboot
Enjoy!
CREDITS:
Emmanuel U for the Ion Kernel and other repo fun
Team KitKatDS for the Device Tree and Vendor Info plus other goodies
TeamSXL
TeamHydra
SilverL
TBalden
thewisenerd
streambinder
galaxyfreak
CyanogenMod
CarbonDev
Did I miss anything? I appreciate the feedback, and any thanks as well!
XDA:DevDB Information
[ROM][EOL][CARBON][KK 4.4.4] CarbonROM (MT4GS), ROM for the T-Mobile myTouch 4G Slide
Contributors
joel.maxuel
Source Code: https://github.com/carbon-mt4gs
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: No Longer Updated
Beta Release Date: 2015-12-13
Created 2015-05-27
Last Updated 2016-08-28

Other Info...
Anyone looking to develop KitKat ROM's for the Doubleshot? This Local Manifest will give you a good start:
If looking to compile updated CarbonROM 4.4.4 for this device, you can start your build environment with:
Code:
mkdir carbon
cd carbon
repo init -u https://github.com/carbon-mt4gs/android.git -b kk && repo sync -f
Then continue all the build steps as normal.

What looks to be the first problem I encountered...camera:
/proc/kmsg
logcat
Essentially (via logcat):
Code:
D/[UCAM]CameraHolder( 9650): Open camera 0
E/CameraService( 170): CameraService::connect X (pid 9650) rejected (invalid cameraId 0).
W/CameraBase( 9650): An error occurred while connecting to camera: 0
E/[UCAM]CameraHolder( 9650): Fail to connect Camera
E/[UCAM]CameraHolder( 9650): java.lang.RuntimeException: Fail to connect to camera service
...and kmsg:
Code:
<4>[ 2831.616455] ------------[ cut here ]------------
<4>[ 2831.616546] WARNING: at /home/joel/carbon/kernel/htc/doubleshot/fs/sysfs/dir.c:455 0xc02879d8()
<4>[ 2831.616668] sysfs: cannot create duplicate filename '/devices/virtual/kgsl/kgsl/proc/9650'
<4>[ 2831.616821] Modules linked in:
<4>[ 2831.616943] Function entered at [<c010cc1c>] from [<c01940e0>]
<4>[ 2831.617034] Function entered at [<c01940e0>] from [<c0194218>]
<4>[ 2831.617156] Function entered at [<c0194218>] from [<c02879d8>]
<4>[ 2831.617218] Function entered at [<c02879d8>] from [<c0287ba0>]
<4>[ 2831.617370] Function entered at [<c0287ba0>] from [<c03c49c4>]
<4>[ 2831.617431] Function entered at [<c03c49c4>] from [<c03c51c0>]
<4>[ 2831.617553] Function entered at [<c03c51c0>] from [<c045c5f8>]
<4>[ 2831.617675] Function entered at [<c045c5f8>] from [<c0457cf4>]
<4>[ 2831.617767] Function entered at [<c0457cf4>] from [<c022c3c4>]
<4>[ 2831.617767] Function entered at [<c022c3c4>] from [<c02252d4>]
<4>[ 2831.617767] Function entered at [<c02252d4>] from [<c02265e0>]
<4>[ 2831.617767] Function entered at [<c02265e0>] from [<c0236c6c>]
<4>[ 2831.617767] Function entered at [<c0236c6c>] from [<c0238630>]
<4>[ 2831.617767] Function entered at [<c0238630>] from [<c0238d28>]
<4>[ 2831.617797] Function entered at [<c0238d28>] from [<c02266e4>]
<4>[ 2831.617797] Function entered at [<c02266e4>] from [<c0106c40>]
<4>[ 2831.617797] ---[ end trace debad88b1f20abd4 ]---
<3>[ 2831.617797] kobject_add_internal failed for 9650 with -EEXIST, don't try to register things with the same name in the same directory.
Well well well, I guess we cannot be perfect, and my work is far from done. Drat.
Guess I may have to commit this? EDIT: I did, and it made no difference.
Just for fun, I also have a logcat from bootup time. Namely of interest:
Code:
E/HAL ( 170): load: module=/system/lib/hw/camera.vendor.msm8660.so
E/HAL ( 170): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters15setPostviewSizeEii" referenced by "camera.vendor.msm8660.so"...
E/CameraWrapper( 170): failed to open vendor camera module

you might need some legacy build parameters for htc camera callbackd, and maybe some patch in the camera header hw part so that the proprietary camera module could fit with the os. I think Emmanuel's repos will contain what you may need.

tbalden said:
you might need some legacy build parameters for htc camera callbackd, and maybe some patch in the camera header hw part so that the proprietary camera module could fit with the os. I think Emmanuel's repos will contain what you may need.
Click to expand...
Click to collapse
Have merged KitKatDS/android_frameworks_av with CarbonDev/android_frameworks_av into my github, hopefully that will work. I figured out the missing parameter, and see in CameraParameters.cpp that it's just a dummy function. But it turns out I needed more than just the function and the call to it. Luckily I could do an automatic merge (because I am not up for the manual way - yet).
Going to be a few more hours compiling before I can figure out if that worked (my poor dual-core PC is working hard ).
Eventually I want to get the CarbonDev commits into android_frameworks_native, but that will be a manual process (3 files to edit by hand) when I looked at the compare.
EDIT: Finished earlier than I thought. And a healthy camera init:
Code:
I/CameraService( 169): CameraService started (pid=169)
I/CameraService( 169): Loaded "MSM8660 Camera Wrapper" camera module
D/libEGL ( 252): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 252): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 252): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL( 252): <qeglDrvAPI_eglInitialize:269>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051_msm8960_JB_VANILLA_CL2997615_release_AU (CL2997615)
I/Adreno200-EGL( 252): Build Date: 04/11/13 Thu
I/Adreno200-EGL( 252): Local Branch:
I/Adreno200-EGL( 252): Remote Branch: quic/mako_jb_mr1
I/Adreno200-EGL( 252): Local Patches: NONE
I/Adreno200-EGL( 252): Reconstruct Branch: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051 + NOTHING
E/cutils-trace( 252): Error opening trace file: No such file or directory (2)
D/QualcommCameraHardwareZSL( 169): int android::HAL_getNumberOfCameras(),return how many camera 2
Torch now works as well, but when I open the stock Camera app (which is now there), I get "Unfortunately, Camera has stopped." Strangely, works fine in UCam. IP Webcam works as well, but I tried a few camcorder apps out there and neither worked.
CLEANUP of old thoughts:
Bootup Logcat
Camera Logcat
Camera Kmsg
Camera Logcat is probably the most interesting here now:
Code:
E/AndroidRuntime( 2454): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2454): Process: com.android.camera2, PID: 2454
E/AndroidRuntime( 2454): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2454): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2454): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2454): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2454): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2454): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2454): at android.os.HandlerThread.run(HandlerThread.java:61)
W/ActivityManager( 481): Force finishing activity com.android.camera2/com.android.camera.CameraLauncher
Not sure what to try here except use the android_frameworks_av off KitKatDS, not CarbonDev's (that had the KitKatDS commits applied to it). I will work on that...compiling has started.
UPDATE: Still broken, logcat is showing the same error. Tried other cameras on this build (Google Camera), and close to the same result.
Camera logcat (Stock, Google ... *:E)
MORE: Realized an important flag was being set twice in the BoardConfigCommon.mk:
Code:
# Camera
BOARD_USES_QCOM_LEGACY_CAM_PARAMS := true
COMMON_GLOBAL_CFLAGS += -DICS_CAMERA_BLOB -DNO_UPDATE_PREVIEW -DQCOM_BSP_CAMERA_ABI_HACK -DQCOM_LEGACY_CAM_PARAMS
BOARD_HAVE_HTC_FFC := true
TARGET_DISABLE_ARM_PIE := true
BOARD_NEEDS_MEMORYHEAPPMEM := true
USE_DEVICE_SPECIFIC_CAMERA := true
BOARD_USES_PMEM_CAMERA := true
I thought maybe LEGACY_CAM_PARAMS were cancelling each other out. Recompiled (without -DQCOM_LEGACY_CAM_PARAMS), No dice.
Latest Camera Logcat. Fatal exception at line 696.
Tried some commits against frameworks/native, still no go:
Code:
E/AndroidRuntime( 2725): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2725): Process: com.android.camera2, PID: 2725
E/AndroidRuntime( 2725): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2725): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2725): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2725): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2725): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2725): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2725): at android.os.HandlerThread.run(HandlerThread.java:61)
I forgot which camera I used for the logcat on my thread post, but if it was the Carbon one, here is what is at line 298 of src/com/android/camera/AndroidCameraManagerImpl.java:
Code:
case SET_FACE_DETECTION_LISTENER:
setFaceDetectionListener((FaceDetectionListener) msg.obj);
return;
So this may be the key. I tried a commit last night, but it didn;t do anything, trying a change to the Gallery2 app that disables the Face Detection on both cameras. We shall see how that goes...
So the latest change involving turning down face detection didn't work. Still getting the same error. A user on StackOverflow pointed out that what I was featuring from the logcat was secondary to the actual problem. That this is a more complete picture:
Code:
E/QualcommCameraHardwareZSL( 170): Invalid focus mode value: continuous-picture
E/QualcommCameraHardwareZSL( 170): virtual android::status_t android::QualcommCameraHardware::setParameters(const android::CameraParameters&): 6487, rc = -22
...
E/AndroidRuntime( 2700): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2700): Process: com.android.camera2, PID: 2700
E/AndroidRuntime( 2700): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2700): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2700): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2700): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2700): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2700): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2700): at android.os.HandlerThread.run(HandlerThread.java:61)
So it was a parameters problem after all! I looked up continuous-picture in (my copy and KitKatDS's) frameworks_av and it is listed, and not hidden behind any #ifdef's. So it should pick up. I just don't know how to tackle this one at this point (if I ever had a clue).
Any further suggestions @Emmanuel U, @thewisenerd, @streambinder, @galaxyfreak, @tbalden? Thanks for all the help so far.

joel.maxuel said:
Have merged KitKatDS/android_frameworks_av with CarbonDev/android_frameworks_av into my github, hopefully that will work. I figured out the missing parameter, and see in CameraParameters.cpp that it's just a dummy function. But it turns out I needed more than just the function and the call to it. Luckily I could do an automatic merge (because I am not up for the manual way - yet).
Going to be a few more hours compiling before I can figure out if that worked (my poor dual-core PC is working hard ).
Eventually I want to get the CarbonDev commits into android_frameworks_native, but that will be a manual process (3 files to edit by hand) when I looked at the compare.
EDIT: Finished earlier than I thought. And a healthy camera init:
Code:
I/CameraService( 169): CameraService started (pid=169)
I/CameraService( 169): Loaded "MSM8660 Camera Wrapper" camera module
D/libEGL ( 252): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 252): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 252): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL( 252): <qeglDrvAPI_eglInitialize:269>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051_msm8960_JB_VANILLA_CL2997615_release_AU (CL2997615)
I/Adreno200-EGL( 252): Build Date: 04/11/13 Thu
I/Adreno200-EGL( 252): Local Branch:
I/Adreno200-EGL( 252): Remote Branch: quic/mako_jb_mr1
I/Adreno200-EGL( 252): Local Patches: NONE
I/Adreno200-EGL( 252): Reconstruct Branch: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051 + NOTHING
E/cutils-trace( 252): Error opening trace file: No such file or directory (2)
D/QualcommCameraHardwareZSL( 169): int android::HAL_getNumberOfCameras(),return how many camera 2
Torch now works as well, but when I open the stock Camera app (which is now there), I get "Unfortunately, Camera has stopped." Strangely, works fine in UCam. IP Webcam works as well, but I tried a few camcorder apps out there and neither worked.
CLEANUP of old thoughts:
Bootup Logcat
Camera Logcat
Camera Kmsg
Camera Logcat is probably the most interesting here now:
Code:
E/AndroidRuntime( 2454): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2454): Process: com.android.camera2, PID: 2454
E/AndroidRuntime( 2454): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2454): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2454): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2454): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2454): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2454): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2454): at android.os.HandlerThread.run(HandlerThread.java:61)
W/ActivityManager( 481): Force finishing activity com.android.camera2/com.android.camera.CameraLauncher
Not sure what to try here except use the android_frameworks_av off KitKatDS, not CarbonDev's (that had the KitKatDS commits applied to it). I will work on that...compiling has started.
UPDATE: Still broken, logcat is showing the same error. Tried other cameras on this build (Google Camera), and close to the same result.
Camera logcat (Stock, Google ... *:E)
MORE: Realized an important flag was being set twice in the BoardConfigCommon.mk:
Code:
# Camera
BOARD_USES_QCOM_LEGACY_CAM_PARAMS := true
COMMON_GLOBAL_CFLAGS += -DICS_CAMERA_BLOB -DNO_UPDATE_PREVIEW -DQCOM_BSP_CAMERA_ABI_HACK -DQCOM_LEGACY_CAM_PARAMS
BOARD_HAVE_HTC_FFC := true
TARGET_DISABLE_ARM_PIE := true
BOARD_NEEDS_MEMORYHEAPPMEM := true
USE_DEVICE_SPECIFIC_CAMERA := true
BOARD_USES_PMEM_CAMERA := true
I thought maybe LEGACY_CAM_PARAMS were cancelling each other out. Recompiled (without -DQCOM_LEGACY_CAM_PARAMS), No dice.
Latest Camera Logcat. Fatal exception at line 696.
Tried some commits against frameworks/native, still no go:
Code:
E/AndroidRuntime( 2725): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2725): Process: com.android.camera2, PID: 2725
E/AndroidRuntime( 2725): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2725): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2725): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2725): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2725): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2725): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2725): at android.os.HandlerThread.run(HandlerThread.java:61)
I forgot which camera I used for the logcat on my thread post, but if it was the Carbon one, here is what is at line 298 of src/com/android/camera/AndroidCameraManagerImpl.java:
Code:
case SET_FACE_DETECTION_LISTENER:
setFaceDetectionListener((FaceDetectionListener) msg.obj);
return;
So this may be the key. I tried a commit last night, but it didn;t do anything, trying a change to the Gallery2 app that disables the Face Detection on both cameras. We shall see how that goes...
So the latest change involving turning down face detection didn't work. Still getting the same error. A user on StackOverflow pointed out that what I was featuring from the logcat was secondary to the actual problem. That this is a more complete picture:
Code:
E/QualcommCameraHardwareZSL( 170): Invalid focus mode value: continuous-picture
E/QualcommCameraHardwareZSL( 170): virtual android::status_t android::QualcommCameraHardware::setParameters(const android::CameraParameters&): 6487, rc = -22
...
E/AndroidRuntime( 2700): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 2700): Process: com.android.camera2, PID: 2700
E/AndroidRuntime( 2700): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2700): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2700): at android.hardware.Camera.setParameters(Camera.java:1696)
E/AndroidRuntime( 2700): at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)
E/AndroidRuntime( 2700): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2700): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 2700): at android.os.HandlerThread.run(HandlerThread.java:61)
So it was a parameters problem after all! I looked up continuous-picture in (my copy and KitKatDS's) frameworks_av and it is listed, and not hidden behind any #ifdef's. So it should pick up. I just don't know how to tackle this one at this point (if I ever had a clue).
Any further suggestions @Emmanuel U, @thewisenerd, @streambinder, @galaxyfreak, @tbalden? Thanks for all the help so far.
Click to expand...
Click to collapse
Lemme compile my own build later today and back to you, I think my github is missing something I have locally

So I just reproduced the error build on my side, I'll be playing around with it later today when I have time.
Edit: so fixed the error with the focus modes, so the camera functions. But now the camcorder isnt working properly. It records but something fails when it stops recording and it doesn't save the video. I'll keep you posted.

Emmanuel U said:
So I just reproduced the error build on my side, I'll be playing around with it later today when I have time.
Edit: so fixed the error with the focus modes, so the camera functions. But now the camcorder isnt working properly. It records but something fails when it stops recording and it doesn't save the video. I'll keep you posted.
Click to expand...
Click to collapse
That was quick! Must be only recompiling the Camera2 apk (never figured out how to do that - although never really looked - except maybe drag the project into Eclipse).
So what is the focus mode fix? I can compile with that and see if my camcorder crashes as well.

joel.maxuel said:
That was quick! Must be only recompiling the Camera2 apk (never figured out how to do that - although never really looked - except maybe drag the project into Eclipse).
So what is the focus mode fix? I can compile with that and see if my camcorder crashes as well.
Click to expand...
Click to collapse
You should always steer away from hacking ROMs to fix an error, as the issue is usually on your side. https://github.com/KitKatDS/android...mmit/6ec8fea20ce4ef854f634b4ad0389986b9e4eb2e

A new rom for my old MyTouch 4G slide?

Dukenukemx said:
A new rom for my old MyTouch 4G slide?
Click to expand...
Click to collapse
That's right.
I wanted to see what compiling from source is like, and since my daily driver (Fx3Q) has a few bits needed before development can be fruitful (need device tree), I figured I would build for the Doubleshot.
As Emman has pointed out, there are so many competing priorities with the newer ROM's thanks to newer devices that older devices can barely keep up and maintain their mark in the existing code.
I don't have the skill set to change that problem, but I will go along and debug away.
This ROM doesn't make any promises, it's just a change in perspective (presenting CarbonROM instead of having CM as the only KitKat ROM). And if I get bored enough in a months time (assuming the major bugs are squashed - I sure hope so), I just might try out another perspective.

So this is my current logcat.
I'm concerned about this line
Code:
E/OMXCodec( 170): [OMX.google.h264.encoder] ERROR(0x80001001, 0)
E/MPEG4Writer( 170): The number of recorded samples is 0
That hex error code points to OMX_ErrorUndefined. I'm thinking I'm overlooking something because the road can't end here haha. I call it quits for tonight because I got a paper due in a few hours, but I'll hop back on it soon.
Edit: btw this is where the camcorder records but when trying to end the recording, it fails and it's like you never recorded a video. I have some local changes, but no point in uploading them yet because they haven't shown any signs of being beneficial. However, my change from before should fix your native_set_parms error. Later, I'm gonna remove a decent amount of unneeded lines from the camerawrapper.

I see this is now your new enemy. How are those wrinkles coming?
Possibly related (further up):
Code:
E/SoftAVCEncoder( 170): Failed to initialize the encoder: -8
E/AudioHardwareMSM8660( 170): cur_rx for pcm playback = 2
So from my view, the crash has to do with checking the video content, but finding a null file.
Makes sense, in my earlier post about finding no camcorder app that actually worked, well, I did find one that didn't crash at the outset (or ever), but it didn't record anything.
Too bad any search for "E/SoftAVCEncoder Failed to initialize the encoder: -8" comes up with four results, all unrelated to our situation.

I'll certainly keep an eye out for this rom. I'd like to bring back the MyTouch4G Slide with a working fast rom.

joel.maxuel said:
I see this is now your new enemy. How are those wrinkles coming?
Possibly related (further up):
Code:
E/SoftAVCEncoder( 170): Failed to initialize the encoder: -8
E/AudioHardwareMSM8660( 170): cur_rx for pcm playback = 2
So from my view, the crash has to do with checking the video content, but finding a null file.
Makes sense, in my earlier post about finding no camcorder app that actually worked, well, I did find one that didn't crash at the outset (or ever), but it didn't record anything.
Too bad any search for "E/SoftAVCEncoder Failed to initialize the encoder: -8" comes up with four results, all unrelated to our situation.
Click to expand...
Click to collapse
Well those errors seem to be inherent from the OMX error, earlier in the logs.

From my question in Stackoverflow:
There are several lists of capabilities that the camera HAL needs to report correctly, including the supported focus modes. The correct list depends on your camera hardware, and the HAL then also needs to accept whatever it advertises as supported. Several keys are mandatory, so just commenting them out may cause other crashes - instead, you should figure out what's actually supported, and include only those values. (Generally, anything that's KEY_SUPPORTED_* you need to set valid values to in the camera HAL)
Click to expand...
Click to collapse
Looks like we cannot just comment out/remove that line, more like remove the offending focus mode (or modes if we find more) from it.

joel.maxuel said:
From my question in Stackoverflow:
Looks like we cannot just comment out/remove that line, more like remove the offending focus mode (or modes if we find more) from it.
Click to expand...
Click to collapse
Yea we can, the problem isn't with the wrapper. That line was never supposed to be there anyway because we don't need to override the detected focus values. It's something in the framework....or else my KitKatDS wouldn't work either. I'm still on a busy streak but I'll dive into it soon I promise lol.

Update later today...
As many may know, Kitkat is end-of-life, or near EOL, depending on the ROM you use. For CarbonROM, it have been EOL for several months now (when the commits stopped occurring), but for CyanogenMod, they are still maintaining critical patches all the way down to CM10.1 (which will probably cease soon).
Because of Stagefright issues, I wanted to re-do CM10.1 at the very least. But I was plagued with build errors. I got a build, but the robbing and stealing I did in the build phase made sure it didn't boot. So it seems CM10.1 is un-buildable at this point.
I then turned to CarbonROM. Because Carbon is close to that of CM in the code, I was able to cherry-pick any new android_frameworks_av commits (where the stagefright problem(s) are found), and get a successful build.
I am pleased to say, unlike out-of-the-box (EOL) CarbonROM 4.4.4, this build is not vulnerable - at least until the next round comes out...D'Oh!
I will be uploading the build tonight. Uploaded - see 1st post.

November 14th build...
...is on AndroidFileHost at the moment, will add to DevDB later today.
In short, this fixes the SF2.0 problems. Will be updating the OP shortly.
Enjoy!

This rom is still being worked on? Does it fully work? Can I finally go back to a QWERTY phone?